Hi Helin Thanks for your advice. However, it's hard to find the original patches which introduced the bug in general, especailly when the file name has changed. This may prevent us to contribute to dpdk. < 4. A 'Cc:' line is needed, if the patch should be back ported into any stable release version. As a common contributor, I don't know whether the patch should be back ported into any stable release version. And I have no rights to make this decision.
Thank you! Yours, Yong ------------------origin------------------ From： <helin.zh...@intel.com>; To：<wang.yon...@zte.com.cn>; <beilei.x...@intel.com>; <wenzhuo...@intel.com>; <fiona.tr...@intel.com>; Cc： <dev@dpdk.org>; Date ：2018-01-24 16:41 Subject ：RE: [dpdk-dev] [PATCH v3 1/3] net/i40e: add null point check andfix mem leak Hi Yong Thank you so much for your contribution! I have comments in general. 1. for a patch set, you need a cover letter for the series. 2. If a patch is to fix a bug/issue, the title should start with 'fix'. 3. A 'Fixes:' line is needed for any bug fixes. 4. A 'Cc:' line is needed, if the patch should be back ported into any stable release version. 5. you can find some good examples from the 'git log'. Thanks! Regards, Helin
