From: Kalle Valo <kvalo@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-wireless@vger.kernel.org,
sebastian.reichel@collabora.co.uk
Subject: Re: wl18xx: NVS file handling
Date: Sat, 23 Apr 2022 09:16:39 +0300 [thread overview]
Message-ID: <87ee1oqq7s.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <YmKaoRfxo4bMzDdR@atomide.com> (Tony Lindgren's message of "Fri, 22 Apr 2022 15:08:01 +0300")
Tony Lindgren <tony@atomide.com> writes:
> * Yegor Yefremov <yegorslists@googlemail.com> [220422 10:40]:
>> Wouldn't we need this functionality [1] to make the NVS fw file optional? :-(
>>
>> [1] https://patchwork.kernel.org/project/linux-dmaengine/patch/20181112160143.4459-1-l.stach@pengutronix.de/
>
> Hmm yeah, how about if we use just an empty nvs file for no warnings then?
What's wrong with firmware_request_nowarn()?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-23 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 13:57 wl18xx: NVS file handling Yegor Yefremov
2022-04-21 5:19 ` Tony Lindgren
2022-04-21 9:01 ` Yegor Yefremov
2022-04-22 10:43 ` Yegor Yefremov
2022-04-22 12:08 ` Tony Lindgren
2022-04-22 12:34 ` Yegor Yefremov
2022-04-23 6:16 ` Kalle Valo [this message]
2022-04-25 6:43 ` Yegor Yefremov
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=87ee1oqq7s.fsf@tynnyri.adurom.net \
--to=kvalo@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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