From: Jakub Kicinski <kuba@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Subject: Re: [stable] bnxt_en: Move devlink_register before registering netdev
Date: Mon, 3 Feb 2020 15:27:55 -0800 [thread overview]
Message-ID: <20200203152755.577057b0@cakuba.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CACKFLi=8uYrOx9GM412hArXzFHZW7WpD3P4F_hT5S0bgf_YTjA@mail.gmail.com>
On Sun, 2 Feb 2020 23:42:00 -0800, Michael Chan wrote:
> David, I'd like to request this patch for 5.4 and 5.5 stable kernels.
> Without this patch, the phys_port_name may not be registered in time
> for the netdev and some users report seeing inconsistent naming of the
> device. Thanks.
>
> commit cda2cab0771183932d6ba73c5ac63bb63decdadf
> Author: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
> Date: Mon Jan 27 04:56:22 2020 -0500
>
> bnxt_en: Move devlink_register before registering netdev
Queued!
next prev parent reply other threads:[~2020-02-03 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 7:42 [stable] bnxt_en: Move devlink_register before registering netdev Michael Chan
2020-02-03 23:27 ` Jakub Kicinski [this message]
2020-02-04 10:55 ` David Miller
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=20200203152755.577057b0@cakuba.hsd1.ca.comcast.net \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vasundhara-v.volam@broadcom.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).