From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Rosen Xu <rosen.xu@intel.com>
Cc: dev@dpdk.org, declan.doherty@intel.com,
bruce.richardson@intel.com, shreyansh.jain@nxp.com,
tianfei.zhang@intel.com, hao.wu@intel.com
Subject: Re: [dpdk-dev] [RFC 0/5] Introduce Intel FPGA BUS
Date: Mon, 19 Mar 2018 10:06:30 +0100 [thread overview]
Message-ID: <20180319090630.gvcffcx4cwet6zgm@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1521097866-58282-1-git-send-email-rosen.xu@intel.com>
Hi Rosen,
On Thu, Mar 15, 2018 at 03:11:06PM +0800, Rosen Xu wrote:
> Intel FPGA BUS in DPDK
> -------------------------
>
> RFC [1]:
> http://www.dpdk.org/ml/archives/dev/2018-March/092297.html
> http://www.dpdk.org/ml/archives/dev/2018-March/092298.html
> http://www.dpdk.org/ml/archives/dev/2018-March/092299.html
> http://www.dpdk.org/ml/archives/dev/2018-March/092300.html
> http://www.dpdk.org/ml/archives/dev/2018-March/092301.html
>
Have you had the time to read the section titled "Contribute
by sending patches" of the Development page from dpdk.org [1]?
You need to generate the new thread with an increased version number (-v
option for git format-patch), generate the patchset using --thread, and
send the new version as a reply to the origin thread cover letter.
These points are important for working over emails and allowing us to
have a clear view of your work.
[1]: http://dpdk.org/dev
Regards,
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2018-03-19 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 7:11 Rosen Xu
2018-03-19 9:06 ` Gaëtan Rivet [this message]
2018-03-19 9:08 ` Xu, Rosen
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=20180319090630.gvcffcx4cwet6zgm@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hao.wu@intel.com \
--cc=rosen.xu@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=tianfei.zhang@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).