From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [PATCH v2 1/3] ethdev: fix MAC changes when live change not supported
Date: Fri, 24 Aug 2018 13:29:46 +0100 [thread overview]
Message-ID: <d4b320e2-4d25-88c0-bed9-2c78f84d9bac@intel.com> (raw)
In-Reply-To: <1535109359-48584-2-git-send-email-alejandro.lucero@netronome.com>
On 8/24/2018 12:15 PM, Alejandro Lucero wrote:
> Current code assumes a MAC change can occur when the port has been
> started. In fact, there are some NICs which require this port state
> for being successful, but other NICs not always support MAC change
> in that case.
>
> This patch supports a new device flag for a device advertising this
> limitation, and if the flag is set, the MAC is changed before the
> port starts.
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
And this looks like behavior change, controlled with a new flag. Do you thinks
is this fix or should be really backported stable trees?
next prev parent reply other threads:[~2018-08-24 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 11:15 support MAC changes when no live changes allowed Alejandro Lucero
2018-08-24 11:15 ` [PATCH v2 1/3] ethdev: fix MAC changes when live change not supported Alejandro Lucero
2018-08-24 12:27 ` Ferruh Yigit
2018-08-24 12:45 ` Alejandro Lucero
2018-08-24 12:29 ` Ferruh Yigit [this message]
2018-08-24 11:15 ` [PATCH v2 2/3] net/nfp: fix live MAC changes " Alejandro Lucero
2018-08-24 11:15 ` [PATCH v2 3/3] doc: comment rte_eth_dev_start change Alejandro Lucero
2018-08-24 12:28 ` Ferruh Yigit
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=d4b320e2-4d25-88c0-bed9-2c78f84d9bac@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.