[Starlingx-discuss] Analysis of patch e547a7e & ebd41fd for StartlingX upstreaming
chenjie.xu at intel.com
Mon Oct 8 03:16:57 UTC 2018
Thank you for your comment! Sorry for the late reply! Last week is our national holiday.
From: Peters, Matt [mailto:Matt.Peters at windriver.com]
Sent: Monday, October 1, 2018 9:12 PM
To: Xu, Chenjie <chenjie.xu at intel.com>
Cc: starlingx-discuss at lists.starlingx.io; Zhao, Forrest <forrest.zhao at intel.com>; Guo, Ruijing <ruijing.guo at intel.com>
Subject: RE: [Starlingx-discuss] Analysis of patch e547a7e & ebd41fd for StartlingX upstreaming
I agree that this is still an issue upstream that needs to be fixed.
From: Xu, Chenjie [mailto:chenjie.xu at intel.com]
Sent: Sunday, September 30, 2018 11:07 AM
To: Peters, Matt
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; Zhao, Forrest; Guo, Ruijing
Subject: [Starlingx-discuss] Analysis of patch e547a7e & ebd41fd for StartlingX upstreaming
For patches e547a7e and ebd41fd, I think it's a bug in Neutron upstream and will submit the patch to fix it in the next step. This bug is caused by passing the wrong parameter after create or update router. You can find the analysis report within attached file. Could you please help review and comment!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Starlingx-discuss