From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Aaron Conole <aconole@redhat.com>,
John Daley <johndale@cisco.com>,
Nelson Escobar <neescoba@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC 0/4] misc enic fixes
Date: Tue, 3 Oct 2017 17:16:54 +0100 [thread overview]
Message-ID: <516d27ee-d2a8-421b-20b8-4a43edbc0791@intel.com> (raw)
In-Reply-To: <20170926185329.2776-1-aconole@redhat.com>
On 9/26/2017 7:53 PM, Aaron Conole wrote:
> These still need some testing, and I will cc to stable
> with the official patch.
>
> I'm especially interested in the comments on base.
>
> Aaron Conole (4):
> enic: update format string to match arg types
> enic: fix assignment
> enic: remove unused code
> enic: remove anscillary assignment
Series Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
And please add the maintainers to cc next time.
Since this is RFC, I assume you will send v1 of the patchset, when
sending v1 can you please add "Fixes:" and "Cc: stable@dpdk.org" tags in
commit log for fixes, these assure patches will be picked by stable tree.
Thanks,
ferruh
next prev parent reply other threads:[~2017-10-03 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 18:53 Aaron Conole
2017-09-26 18:53 ` [dpdk-dev] [RFC 1/4] enic: update format string to match arg types Aaron Conole
2017-10-10 17:30 ` John Daley (johndale)
2017-09-26 18:53 ` [dpdk-dev] [RFC 2/4] enic: fix assignment Aaron Conole
2017-10-10 17:31 ` John Daley (johndale)
2017-09-26 18:53 ` [dpdk-dev] [RFC 3/4] enic: remove unused code Aaron Conole
2017-10-10 17:31 ` John Daley (johndale)
2017-09-26 18:53 ` [dpdk-dev] [RFC 4/4] enic: remove anscillary assignment Aaron Conole
2017-10-10 17:32 ` John Daley (johndale)
2017-10-03 16:16 ` Ferruh Yigit [this message]
2017-10-09 14:00 ` [dpdk-dev] [RFC 0/4] misc enic fixes Aaron Conole
2017-10-10 23:06 ` Ferruh Yigit
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=516d27ee-d2a8-421b-20b8-4a43edbc0791@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.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).