[Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming
Fang, Liang A
liang.a.fang at intel.com
Tue Nov 6 14:17:29 UTC 2018
From: Badea, Daniel [mailto:Daniel.Badea at windriver.com]
Sent: Tuesday, November 6, 2018 10:03 PM
To: Fang, Liang A <liang.a.fang at intel.com>; Poncea, Ovidiu <Ovidiu.Poncea at windriver.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming
No objections here, mark this patch as abandoned.
From: Fang, Liang A [liang.a.fang at intel.com]
Sent: Tuesday, November 06, 2018 10:55
To: Badea, Daniel; Poncea, Ovidiu
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming
Hi Daniel and Ovidiu
Title: Pike Rebase: Fix Cinder memory leak
This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Starlingx-discuss