From: "John Daley (johndale)" <johndale@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] enic flow director fixes
Date: Thu, 9 Feb 2017 17:44:08 +0000 [thread overview]
Message-ID: <f609847d17cc45d3baa8faf1ed071da3@XCH-RCD-007.cisco.com> (raw)
In-Reply-To: <2a7ba108-ddd4-acf7-cba3-bc6c9cb4716b@intel.com>
> -----Original Message-----
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Thursday, February 09, 2017 4:15 AM
> To: John Daley (johndale) <johndale@cisco.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v2] enic flow director fixes
>
> On 2/9/2017 12:40 AM, John Daley wrote:
> > This should replace
> > http://www.dpdk.org/dev/patchwork/patch/20147/ which was an
> > intermediate patch in a small patchset and had a compile error. Also,
> > please reject the 2nd patch in the patchset
> > http://www.dpdk.org/dev/patchwork/patch/20148/ which is incomplete. I
> will change the state of these patches in patchworks.
> > thank you, john
>
> Hi John,
>
> I dropped the previous two and will get this one. And this looks like the
> squashed version of the previous two with some updates in ipv6 shift
> number.
>
> Although next-net can re-write the git history, this is mainly to provide ability
> to rebasing on master tree. Not for amending patches on fly, that is
> confusing.
>
> Please next time do not rely on git history re-writing while sending patches.
Oops I was stupidly looking at master and assumed the patches were rejected because of the compile error. I obviously should have been looking at next-net.
Thanks,
John
>
> Thanks,
> ferruh
>
> >
> > John Daley (1):
> > net/enic: fix hardcoding of some flow director masks
> >
> > drivers/net/enic/enic_clsf.c | 14 +++++++-------
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
prev parent reply other threads:[~2017-02-09 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 9:54 [dpdk-dev] [PATCH 1/2] net/enic: fix hardcoding of some flow director masks John Daley
2017-02-03 9:54 ` [dpdk-dev] [PATCH 2/2] net/enic: fix flow director IPv6 traffic class specification John Daley
2017-02-03 22:54 ` [dpdk-dev] [PATCH 1/2] net/enic: fix hardcoding of some flow director masks Ferruh Yigit
2017-02-09 0:40 ` [dpdk-dev] [PATCH v2] enic flow director fixes John Daley
2017-02-09 0:40 ` [dpdk-dev] [PATCH v2] net/enic: fix hardcoding of some flow director masks John Daley
2017-02-09 10:16 ` Ferruh Yigit
2017-02-09 17:43 ` John Daley (johndale)
2017-02-09 17:58 ` Ferruh Yigit
2017-02-09 12:21 ` Ferruh Yigit
2017-02-09 12:15 ` [dpdk-dev] [PATCH v2] enic flow director fixes Ferruh Yigit
2017-02-09 17:44 ` John Daley (johndale) [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=f609847d17cc45d3baa8faf1ed071da3@XCH-RCD-007.cisco.com \
--to=johndale@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).