From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [DPDK] net/ice/base: adjust code order and cleanup coding style
Date: Wed, 15 Jul 2020 02:23:25 +0000 [thread overview]
Message-ID: <DM6PR11MB3723CC8584AC9804D5B44BE4E77E0@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a28bdcad-7d64-9f03-89ac-c2c7fe70a81b@intel.com>
Thank you, Ferruh!
> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Monday, July 13, 2020 21:55
> To: Guo, Junfeng <junfeng.guo@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [DPDK] net/ice/base: adjust code order and cleanup coding style
>
> On 7/13/2020 12:05 PM, Junfeng Guo wrote:
> > Previous logic in removing RSS for GTPU was added in incorrect lines.
> > The adjustment in this patch will correct the code order so that RSS
> > for GTPU can be removed successfully.
> >
> > We also delete the redundant print statement and cleanup the coding
> > style in this patch.
> >
> > Fixes: bed9bb3139ef ("net/ice/base: fix GTP-U inner RSS IPv4 IPv6
> > co-exist")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied to dpdk-next-net/master, thanks.
>
>
> Thanks Junfeng for catching this,
> This was already fixed in next-net-intel, somehow seems lost in the next-net,
> fixed now.
next prev parent reply other threads:[~2020-07-15 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 11:05 Junfeng Guo
2020-07-13 13:54 ` Ferruh Yigit
2020-07-15 2:23 ` Guo, Junfeng [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 11:04 Junfeng Guo
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=DM6PR11MB3723CC8584AC9804D5B44BE4E77E0@DM6PR11MB3723.namprd11.prod.outlook.com \
--to=junfeng.guo@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@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).