From: "Dai, Wei" <wei.dai@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"harish.patil@cavium.com" <harish.patil@cavium.com>,
"rasesh.mody@cavium.com" <rasesh.mody@cavium.com>,
"stephen.hurd@broadcom.com" <stephen.hurd@broadcom.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Chen, Jing D" <jing.d.chen@intel.com>,
"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>,
"nelio.laranjeiro@6wind.com" <nelio.laranjeiro@6wind.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"shepard.siegel@atomicrules.com" <shepard.siegel@atomicrules.com>,
"ed.czeck@atomicrules.com" <ed.czeck@atomicrules.com>,
"john.miller@atomicrules.com" <john.miller@atomicrules.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v6 1/3] ethdev: fix adding invalid MAC addr
Date: Fri, 5 May 2017 00:16:16 +0000 [thread overview]
Message-ID: <49759EB36A64CF4892C1AFEC9231E8D650A7968C@PGSMSX106.gar.corp.intel.com> (raw)
In-Reply-To: <20170503014601.GC3005@yliu-dev.sh.intel.com>
> Subject: Re: [PATCH v6 1/3] ethdev: fix adding invalid MAC addr
>
> On Tue, May 02, 2017 at 08:44:23PM +0800, Wei Dai wrote:
> > Some customers find adding MAC addr to VF sometimes can fail, but it
> > is still stored in dev->data->mac_addrs[ ]. So this can lead to some
> > errors that assumes the non-zero entry in
> > dev->data->mac_addrs[ ] is valid.
> > Following acknowledgements are from specific NIC PMD maintainer for
> > their managing part.
> >
> > Fixes: af75078fece3 ("first public release")
>
>
> > Cc: stable@dpdk.org
>
> Just a note, this patch changes API. It should not be backported to a stable/LTS
> release, even though it fixes something.
>
> --yliu
Thank you, Yuanhan. I will drop the "Cc: stable@dpdk.org" in my v7 patch set.
prev parent reply other threads:[~2017-05-05 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1493525507-56304-1-git-send-email-wei.dai@intel.com>
2017-04-30 4:11 ` [dpdk-stable] [PATCH v5 " Wei Dai
[not found] ` <1493729065-17090-1-git-send-email-wei.dai@intel.com>
2017-05-02 12:44 ` [dpdk-stable] [PATCH v6 " Wei Dai
2017-05-03 0:57 ` Lu, Wenzhuo
2017-05-03 1:46 ` Yuanhan Liu
2017-05-05 0:16 ` Dai, Wei [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=49759EB36A64CF4892C1AFEC9231E8D650A7968C@PGSMSX106.gar.corp.intel.com \
--to=wei.dai@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=harish.patil@cavium.com \
--cc=helin.zhang@intel.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.miller@atomicrules.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=rasesh.mody@cavium.com \
--cc=shepard.siegel@atomicrules.com \
--cc=stable@dpdk.org \
--cc=stephen.hurd@broadcom.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.com \
--cc=yuanhan.liu@linux.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).