DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] mempool: remove a redundant word "for" in comment
Date: Mon, 5 Dec 2016 03:06:25 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA01FFAFEF@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <20161128142518.6ed7b6e0@platinum>

Hi, olivier

> -----Original Message-----
> From: Olivier Matz [mailto:olivier.matz@6wind.com]
> Sent: Monday, November 28, 2016 9:25 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v2] mempool: remove a redundant word "for" in
> comment
> 
> Hi Wei,
> 
> On Mon, 28 Nov 2016 09:42:12 +0100
> Olivier Matz <olivier.matz@6wind.com> wrote:
> > Hi Wenzhuo,
> 
> First, sorry for the mistake in your name my previous mail.
> 
> Please find below some other comments about the patch (on the form).
> 
> > On Sun, 27 Nov 2016 10:43:47 +0800
> > Wei Zhao <wei.zhao1@intel.com> wrote:
> >
> > > From: zhao wei <wei.zhao1@intel.com>
> > >
> > > There is a redundant repetition word "for" in commnet line of the
> 
> commnet -> comment
> 
> > > file rte_mempool.h after the definition of
> RTE_MEMPOOL_OPS_NAMESIZE.
> > > The word "for"appear twice in line 359 and 360.One of them is
> 
> Missing space after '"for"' and after '360.'
> 
> 
> > > redundant, so delete it.
> > >
> > > Fixes: 449c49b93a6b (" mempool: support handler operations")
> 
> We should have an empty line after the 'Fixes:' tag. The check-git-log.sh can
> help you to notice these errors.
> 
> Also, it is important that no spaces are added in the title of the commit. You
> can get the exact line with:
>   git log -1 --abbrev=12 --format='Fixes: %h (\"%s\")' <commitid>
> 
> > > Signed-off-by: zhao wei <wei.zhao1@intel.com>
> 
> The name in your .gitconfig should be the same than in you mail:
> Wei Zhao <wei.zhao1@intel.com>
> 
> > > Acked-by: John McNamara <john.mcnamara@intel.com>
> >
> > Acked-by: Olivier Matz <olivier.matz@6wind.com>
> >
> 
> Please, could you also check the same comments in the other patch?
> 
> Last thing: when doing another version of the patch, you should add a
> changelog that describes what was modified. They take place after the 3
> dashes.
> 
> Thank you for contributing.
> 
> Regards,
> Olivier

Thank you for your nicely guide to me,  I have found that I miss using check patch tool  last time.

      reply	other threads:[~2016-12-05  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27  2:43 Wei Zhao
2016-11-28  8:42 ` Olivier Matz
2016-11-28 13:25   ` Olivier Matz
2016-12-05  3:06     ` Zhao1, Wei [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=A2573D2ACFCADC41BB3BE09C6DE313CA01FFAFEF@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).