From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] deadline notice
Date: Thu, 11 Jun 2015 13:39:54 +0200 [thread overview]
Message-ID: <1910067.s2MvseVWWd@xps13> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C204A2E551@IRSMSX108.ger.corp.intel.com>
2015-06-11 10:04, Iremonger, Bernard:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Note: [RFC] should be preferred for incomplete patches or trials.
>
> Should RFC PATCH be retained for v2 and subsequent patches or should RFC be dropped?
If you target an integration of your patch, the RFC keyword must be dropped.
prev parent reply other threads:[~2015-06-11 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 18:39 Thomas Monjalon
2015-06-10 21:13 ` Abdul, Jaffar
2015-06-11 14:00 ` Thomas Monjalon
2015-06-11 1:30 ` Tetsuya Mukawa
2015-06-11 8:34 ` Thomas Monjalon
2015-06-11 9:20 ` Tetsuya Mukawa
2015-06-11 7:27 ` Simon Kagstrom
2015-06-11 8:33 ` Thomas Monjalon
2015-06-11 8:45 ` Simon Kagstrom
2015-06-11 9:30 ` Iremonger, Bernard
2015-06-11 9:58 ` Thomas Monjalon
2015-06-11 10:04 ` Iremonger, Bernard
2015-06-11 11:39 ` Thomas Monjalon [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=1910067.s2MvseVWWd@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bernard.iremonger@intel.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).