From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Benson, Bryan" <bmbenson@amazon.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] RX checksum offloading
Date: Fri, 8 Nov 2013 11:27:50 +0100 [thread overview]
Message-ID: <201311081127.50724.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <A029A4295D154649BCC3E22A692B26022E3E9B@ex10-mbx-36002.ant.amazon.com>
07/11/2013 22:50, Benson, Bryan :
> I have prepared a patch for the issue. If it is not in the correct format,
> please advise.
First of all, thank you for the patch.
My comments on the format:
1) The content type is quoted-printable. So it cannot be applied wihtout
modifications.
Please use git-send-email to send patches.
2) Please set a shorter title and longer explanation in the commit log.
Guidelines should be written on the web site. Probably coming soon.
--
Thomas
next prev parent reply other threads:[~2013-11-08 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 21:50 Benson, Bryan
2013-11-08 10:27 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 0:00 Benson, Bryan
2013-11-07 3:09 ` Benson, Bryan
2013-11-07 3:44 ` Benson, Bryan
2013-11-07 9:06 ` Thomas Monjalon
2013-11-07 11:44 ` Thomas Monjalon
2013-11-07 21:53 ` Benson, Bryan
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=201311081127.50724.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=bmbenson@amazon.com \
--cc=dev@dpdk.org \
/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).