From: wang.yong19@zte.com.cn
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, shepard.siegel@atomicrules.com
Subject: [dpdk-dev] 答复: Re: [PATCH] net/ark:add null point check
Date: Thu, 14 Sep 2017 17:58:10 +0800 [thread overview]
Message-ID: <OF7E84BB99.450C64C3-ON4825819B.00369C74-4825819B.0036B6D0@zte.com.cn> (raw)
In-Reply-To: <89a345e1-43ba-2a2a-4cd2-55e2bad1817d@intel.com>
> Ferruh Yigit <ferruh.yigit@intel.com>
> 2017/09/14 17:33
>
> to
>
> Yong Wang <wang.yong19@zte.com.cn>, shepard.siegel@atomicrules.com,
>
> cc
>
> dev@dpdk.org
>
> subject
>
> Re: [dpdk-dev] [PATCH] net/ark:add null point check
>
> On 9/14/2017 8:22 AM, Yong Wang wrote:
> > In function ark_config_device(), there are several malloc without null
> > point check. Fix it by adding null point check.
> >
> > Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
>
> Hi Yong,
>
> Thank you for the patch.
>
> I think you have sent new version of the patch because previous one was
> giving checkpatch warning, but having two patches with same title is
> being confusing.
>
> Next time would you mind sending next version as version 2 (v2) and as a
> reply to previous version of the patch? So this makes clear which one is
> the one to take into account.
> Also adding a changelog to the commit log makes life easy. Thanks.
>
> DPDK Contributor's Guide has more details:
> http://dpdk.org/doc/guides/contributing/patches.html
>
> Thanks,
> ferruh
Ok. Thanks for your advice.
prev parent reply other threads:[~2017-09-14 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 7:22 [dpdk-dev] " Yong Wang
2017-09-14 9:33 ` Ferruh Yigit
2017-09-14 9:58 ` 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=OF7E84BB99.450C64C3-ON4825819B.00369C74-4825819B.0036B6D0@zte.com.cn \
--to=wang.yong19@zte.com.cn \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shepard.siegel@atomicrules.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).