From: Greg KH <greg@kroah.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: stable@vger.kernel.org, thibaut.collet@6wind.com,
jean-mickael.guerin@6wind.com,
alfonso.sanchez-beato@canonical.com,
Michael Chan <michael.chan@broadcom.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH stable v5.4] bnxt_en: Remove the setting of dev_port.
Date: Tue, 8 Jun 2021 16:56:24 +0200 [thread overview]
Message-ID: <YL+FGIKepS2B0knc@kroah.com> (raw)
In-Reply-To: <20210608144621.668749-1-krzysztof.kozlowski@canonical.com>
On Tue, Jun 08, 2021 at 04:46:21PM +0200, Krzysztof Kozlowski wrote:
> From: Michael Chan <michael.chan@broadcom.com>
>
> commit 1d86859fdf31a0d50cc82b5d0d6bfb5fe98f6c00 upstream.
>
> The dev_port is meant to distinguish the network ports belonging to
> the same PCI function. Our devices only have one network port
> associated with each PCI function and so we should not set it for
> correctness.
>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>
> ---
>
> For stable v5.4. Earlier could work as well, just did not check.
>
> Reported for Ubuntu backport here:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 1 -
> 1 file changed, 1 deletion(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-06-08 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:46 [PATCH stable v5.4] bnxt_en: Remove the setting of dev_port Krzysztof Kozlowski
2021-06-08 14:56 ` Greg KH [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=YL+FGIKepS2B0knc@kroah.com \
--to=greg@kroah.com \
--cc=alfonso.sanchez-beato@canonical.com \
--cc=davem@davemloft.net \
--cc=jean-mickael.guerin@6wind.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=michael.chan@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=thibaut.collet@6wind.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 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.