From: Jakub Kicinski <kuba@kernel.org>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
<sgoutham@marvell.com>, <netdev@vger.kernel.org>,
Harman Kalra <hkalra@marvell.com>
Subject: Re: [net v2 PATCH 2/5] octeontx2-af: suppress external profile loading warning
Date: Wed, 27 Jul 2022 19:51:28 -0700 [thread overview]
Message-ID: <20220727195128.3a5b4297@kernel.org> (raw)
In-Reply-To: <20220727194120.62af8ee7@kernel.org>
On Wed, 27 Jul 2022 19:41:20 -0700 Jakub Kicinski wrote:
> On Tue, 26 Jul 2022 19:41:19 +0530 Subbaraya Sundeep wrote:
> > - if (!request_firmware(&fw, kpu_profile, rvu->dev)) {
> > + if (!firmware_request_nowarn(&fw, kpu_profile, rvu->dev)) {
>
> Consider switching to request_firmware_direct() in net-next.
> I doubt you need the sysfs fallback, I think udev dropped
> the support for it.
Well, the next patch needs work, so perhaps do it in v3?
next prev parent reply other threads:[~2022-07-28 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 14:11 [net v2 PATCH 0/5] Octeontx2 AF driver fixes for NPC Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 1/5] octeontx2-af: Apply tx nibble fixup always Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 2/5] octeontx2-af: suppress external profile loading warning Subbaraya Sundeep
2022-07-28 2:41 ` Jakub Kicinski
2022-07-28 2:51 ` Jakub Kicinski [this message]
2022-07-26 14:11 ` [net v2 PATCH 3/5] octeontx2-af: Allow mkex profiles without dmac Subbaraya Sundeep
2022-07-28 2:51 ` Jakub Kicinski
2022-07-26 14:11 ` [net v2 PATCH 4/5] octeontx2-af: Fix mcam entry resource leak Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 5/5] octeontx2-af: Fix key checking for source mac Subbaraya Sundeep
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=20220727195128.3a5b4297@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkalra@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).