From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Liu, KevinX" <kevinx.liu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Yang, SteveX" <stevex.yang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH v2] net/ice: fix missing MTU value setting
Date: Sat, 4 Jun 2022 01:21:53 +0000 [thread overview]
Message-ID: <DM4PR11MB59944E56864666B6C18B0DDCD7A09@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3613209.MHq7AAxBmi@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, June 3, 2022 5:17 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Liu, KevinX <kevinx.liu@intel.com>; dev@dpdk.org; stable@dpdk.org; Yang,
> Qiming <qiming.yang@intel.com>; Yang, SteveX <stevex.yang@intel.com>;
> stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>;
> ferruh.yigit@amd.com; andrew.rybchenko@oktetlabs.ru
> Subject: Re: [PATCH v2] net/ice: fix missing MTU value setting
>
> 18/05/2022 05:48, Zhang, Qi Z:
> > > From: Liu, KevinX <kevinx.liu@intel.com>
> > > Subject: [PATCH v2] net/ice: fix missing MTU value setting
> > >
> > > In the DCF module, Missing maximum and minimum MTU value settings.
> > >
> > > This patch adds the settings of the maximum and minimum MTU to
> > > correctly calculate the MTU value.
> > >
> > > Fixes: bf89db4409bb ("net/ice: complete device info get in DCF")
> > > Cc: stable@dpdk.org
> >
> > Fix for current version no need cc stable.
>
> It is a patch from 20.08, so need Cc stable.
Yes, it is. I messed it up with another patch , have fixed this in dpdk-next-net-intel.
> In any case, you should run devtools/check-git-log.sh
Of cause I did. but I didn't notice the tool will skip cc stable warning if the fix belongs to the current release, thanks for you hint.
>
>
next prev parent reply other threads:[~2022-06-04 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 19:57 [PATCH] " Kevin Liu
2022-04-08 1:43 ` [PATCH v2] " Kevin Liu
2022-05-18 3:48 ` Zhang, Qi Z
2022-06-03 9:17 ` Thomas Monjalon
2022-06-04 1:21 ` Zhang, Qi Z [this message]
2022-05-17 7:49 ` [PATCH] " Zhang, Qi Z
2022-05-17 7:59 ` Liu, KevinX
2022-05-17 8:06 ` Liu, KevinX
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=DM4PR11MB59944E56864666B6C18B0DDCD7A09@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=kevinx.liu@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=thomas@monjalon.net \
/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).