All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ariel Elior <aelior@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Manish Chopra <manishc@marvell.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Alok Prasad <palok@marvell.com>,
	Prabhakar Kushwaha <pkushwaha@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"it+netdev@molgen.mpg.de" <it+netdev@molgen.mpg.de>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: RE: [EXT] Re: [PATCH v2 net-next 1/2] bnx2x: Utilize firmware 7.13.21.0
Date: Thu, 10 Mar 2022 19:14:14 +0000	[thread overview]
Message-ID: <PH0PR18MB465582071EDA502A96E57096C40B9@PH0PR18MB4655.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220310105232.66f0a429@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

> On Wed, 9 Mar 2022 14:18:23 -0800 Linus Torvalds wrote:
> > On Wed, Mar 9, 2022 at 11:46 AM Manish Chopra <manishc@marvell.com>
> wrote:
> > >
> > > This has not changed anything functionally from driver/device
> perspective, FW is still being loaded only when device is opened.
> > > bnx2x_init_firmware() [I guess, perhaps the name is misleading] just
> request_firmware() to prepare the metadata to be used when device will be
> opened.
> >
> > So how do you explain the report by Paul Menzel that things used to
> > work and no longer work now?
> >
> > You can't do request_firmware() early. When you actually then push the
> > firmware to the device is immaterial - but request_firmware() has to
> > be done after the system is up and running.
> 
> Alright, I don't see a revert in my inbox, so let me double check.
> 
> Linus, is my understanding correct that our PR today should revert
> the patches in question [1]? Or just drop them from stable for now,
> and give Manish and team a week or two to figure out a fix?
> 
> Manish, assuming it's the former - would you be able to provide
> a revert within a couple of hours (and I mean  "couple" in the
> British sense of roughly two)?
> 
> [1] patches in question:
>  e13ad1443684 ("bnx2x: fix driver load from initrd")
>  802d4d207e75 ("bnx2x: Invalidate fastpath HSI version for VFs")
>  b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")

Jackub, assuming former, we won't be able to provide anything in a couple of hours
(already past midnight in Manish's part of the world).

Linus, does "you can't request FW before system is up and running" translate to
"don't request FW at probe" or "don't request FW in initrd?"
Or perhaps something else?

Thanks,
Ariel

  reply	other threads:[~2022-03-10 19:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 16:55 [PATCH v2 net-next 1/2] bnx2x: Utilize firmware 7.13.21.0 Manish Chopra
2021-12-17 16:55 ` [PATCH v2 net-next 2/2] bnx2x: Invalidate fastpath HSI version for VFs Manish Chopra
2022-03-09 16:15 ` [PATCH v2 net-next 1/2] bnx2x: Utilize firmware 7.13.21.0 Paul Menzel
2022-03-09 16:18   ` Paul Menzel
2022-03-09 16:35     ` Jakub Kicinski
2022-03-10 10:13     ` Thorsten Leemhuis
2022-03-11 13:09       ` [PATCH v2 net-next 1/2] bnx2x: Utilize firmware 7.13.21.0 #forregzbot Thorsten Leemhuis
2022-03-09 16:46   ` [EXT] Re: [PATCH v2 net-next 1/2] bnx2x: Utilize firmware 7.13.21.0 Manish Chopra
2022-03-09 18:00     ` Paul Menzel
2022-03-09 19:22       ` Manish Chopra
2022-03-09 19:24         ` Linus Torvalds
2022-03-09 19:46           ` Manish Chopra
2022-03-09 22:18             ` Linus Torvalds
2022-03-10 18:52               ` Jakub Kicinski
2022-03-10 19:14                 ` Ariel Elior [this message]
2022-03-10 19:42                   ` Jakub Kicinski
2022-03-11 12:11               ` Manish Chopra
2022-03-11 12:52                 ` Greg KH
2022-03-11 13:00                 ` Paul Menzel
2022-03-14 14:36                 ` Donald Buczek
2022-03-14 15:07                   ` Paul Menzel
2022-03-15  2:57                     ` Jakub Kicinski
2022-03-16 17:14                       ` Paul Menzel
2022-03-16 11:23                     ` Manish Chopra

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=PH0PR18MB465582071EDA502A96E57096C40B9@PH0PR18MB4655.namprd18.prod.outlook.com \
    --to=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=it+netdev@molgen.mpg.de \
    --cc=kuba@kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=palok@marvell.com \
    --cc=pkushwaha@marvell.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.