From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Luca Boccassi <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>
Subject: Re: [dpdk-stable] [PATCH v2] net/iavf: support multicast configuration
Date: Wed, 28 Oct 2020 11:32:16 +0000 [thread overview]
Message-ID: <23ee4b33f398401c893b0ac6318e1642@intel.com> (raw)
In-Reply-To: <faf0de58bbb6f5df46ebd7c3bd68ee7be24b799d.camel@debian.org>
> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Wednesday, October 28, 2020 7:20 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: stable@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Zhao1, Wei
> <wei.zhao1@intel.com>
> Subject: Re: [dpdk-stable] [PATCH v2] net/iavf: support multicast configuration
>
> On Sat, 2020-10-10 at 10:53 +0800, Qi Zhang wrote:
> > [ upstream commit 05e4c3aff35f41d527acfab86df55477fd8dcff2 ]
> >
> > This patch enable add multicast address for iavf.
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> > ---
> >
> > To maintainer:
> >
> > I know this is not a fix, but this is requested by an important
> > customer that will use DPDK 19.11 LTS, meanwhile this patch just add a
> > missing eth_dev op in AVF, it has low risk to bring any side effect.
> >
> > doc/guides/nics/features/iavf.ini | 1 +
> > drivers/net/iavf/iavf.h | 7 ++++
> > drivers/net/iavf/iavf_ethdev.c | 43 ++++++++++++++++++++++++
> > drivers/net/iavf/iavf_vchnl.c | 56
> +++++++++++++++++++++++++++++++
> > 4 files changed, 107 insertions(+)
>
> Next time please follow the guidelines and use --subject-prefix='PATCH 19.11'
> when sending, otherwise the mail gets filtered out.
Got it, thanks.
>
> What happens if someone upgrades from 19.11.6 with this patch, to say
> 20.08 which doesn't have it? Are there hard errors, or will the feature simply
> be ignored?
I think the unsupported error should be returned.
but I don't think this will be the real case, usually when a user current stick on 19.11 decide to upgrade, it will move to 20.11 directly.
Thanks
Qi
>
> --
> Kind regards,
> Luca Boccassi
prev parent reply other threads:[~2020-10-28 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 2:53 Qi Zhang
2020-10-28 11:20 ` Luca Boccassi
2020-10-28 11:32 ` Zhang, Qi Z [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=23ee4b33f398401c893b0ac6318e1642@intel.com \
--to=qi.z.zhang@intel.com \
--cc=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=wei.zhao1@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).