DPDK patches and discussions
 help / color / mirror / Atom feed
From: <wang.yong19@zte.com.cn>
To: <helin.zhang@intel.com>
Cc: <beilei.xing@intel.com>, <wenzhuo.lu@intel.com>,
	<fiona.trahe@intel.com>,  <dev@dpdk.org>
Subject: [dpdk-dev] 答复: RE:  [PATCH v3 1/3] net/i40e: add null point check andfix	mem leak
Date: Wed, 24 Jan 2018 17:28:26 +0800 (CST)	[thread overview]
Message-ID: <201801241728265136033@zte.com.cn> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AD2055C@SHSMSX103.ccr.corp.intel.com>

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.zhang@intel.com>;
To:<wang.yong19@zte.com.cn>; <beilei.xing@intel.com>; <wenzhuo.lu@intel.com>; <fiona.trahe@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

      reply	other threads:[~2018-01-24  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  2:44 [dpdk-dev] [PATCH v3 1/3] net/i40e: add null point check and fix " Yong Wang
2018-01-23  2:44 ` [dpdk-dev] [PATCH v3 2/3] net/e1000: add null point check for rte_zmalloc Yong Wang
2018-01-23  2:45 ` [dpdk-dev] [PATCH v3 3/3] crypto/qat: add null point check and fix mem leak Yong Wang
2018-01-23 12:16   ` Trahe, Fiona
2018-01-23 12:16   ` [dpdk-dev] [PATCH v3 3/3] crypto/qat: hebing " Trahe, Fiona
2018-01-24  8:41 ` [dpdk-dev] [PATCH v3 1/3] net/i40e: " Zhang, Helin
2018-01-24  9:28   ` wang.yong19 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201801241728265136033@zte.com.cn \
    --to=wang.yong19@zte.com.cn \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=wenzhuo.lu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).