DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Add Rx error statistics for Fortville
Date: Thu, 16 Oct 2014 00:55:38 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A79C8E1@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1416793.NVMu20orOd@xps13>

Hi Thomas

Thank you very much for the detailed guidance! It is really helpful for me.

Regards,
Helin

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, October 15, 2014 8:22 PM
> To: Zhang, Helin
> Cc: dev@dpdk.org; Liu, Jijiang
> Subject: Re: [dpdk-dev] [PATCH] Add Rx error statistics for Fortville
> 
> Helin,
> 
> As you are in charge of i40e, here are 2 tips to acknowledge patches:
> 
> 1) title should take this format:
> 	i40e: add Rx error statistics
> 
> > Acked-by: Helin Zhang <helin.zhang@intel.com>
> 
> 2) This line should be added right after the Signed-off-by.
> And the rest of the email (patch body) can be removed.
> This way, your answer would be faster to read.
> 
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jijiang Liu
> > > Sent: Wednesday, October 15, 2014 11:15 AM
> > > To: dev@dpdk.org
> > > Subject: [dpdk-dev] [PATCH] Add Rx error statistics for Fortville
> 
> This header is not needed also.
> 
> > > This patch adds incoming packet error statistics in the i40e_ethdev.c file.
> > >
> > > Signed-off-by: Jijiang Liu <jijiang.liu@intel.com>
> 
> [I remove the rest of the original email because I have no comment on it]
> 
> Thanks
> --
> Thomas

  reply	other threads:[~2014-10-16  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  3:14 Jijiang Liu
2014-10-15  6:54 ` Zhang, Helin
2014-10-15 12:21   ` Thomas Monjalon
2014-10-16  0:55     ` Zhang, Helin [this message]
2014-10-15 12:25   ` Thomas Monjalon

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A79C8E1@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).