From: Kalle Valo <kvalo@codeaurora.org>
To: Andres Rodriguez <andresx7@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
mcgrof@kernel.org, alexdeucher@gmail.com,
ckoenig.leichtzumerken@gmail.com, arend.vanspriel@broadcom.com,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 8/9] ath10k: use request_firmware_nowarn to load firmware
Date: Fri, 20 Apr 2018 13:19:06 +0300 [thread overview]
Message-ID: <87lgdii3j9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180417153307.3693-9-andresx7@gmail.com> (Andres Rodriguez's message of "Tue, 17 Apr 2018 11:33:06 -0400")
(adding linux-wireless and ath10k lists)
Andres Rodriguez <andresx7@gmail.com> writes:
> This reduces the unnecessary spew when trying to load optional firmware:
> "Direct firmware load for ... failed with error -2"
>
> Signed-off-by: Andres Rodriguez <andresx7@gmail.com>
> ---
> drivers/net/wireless/ath/ath10k/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Kalle Valo <kvalo@codeaurora.org>
But I think it would be good to change also request_firmware_direct() in
ath10k/testmode.c to request_firmware_nowarn().
--
Kalle Valo
next parent reply other threads:[~2018-04-20 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180417153307.3693-1-andresx7@gmail.com>
[not found] ` <20180417153307.3693-9-andresx7@gmail.com>
2018-04-20 10:19 ` Kalle Valo [this message]
[not found] ` <20180417153307.3693-10-andresx7@gmail.com>
2018-04-20 10:26 ` [PATCH 9/9] brcmfmac: use request_firmware_nowait2 to load firmware without warnings Kalle Valo
2018-04-20 19:33 ` Andres Rodriguez
2018-04-21 7:19 ` Kalle Valo
2018-04-21 8:04 ` Arend van Spriel
2018-04-23 13:54 ` Kalle Valo
2018-04-23 20:11 [PATCH 0/9] Loading optional firmware v4 Andres Rodriguez
2018-04-23 20:12 ` [PATCH 8/9] ath10k: use request_firmware_nowarn to load firmware Andres Rodriguez
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=87lgdii3j9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=alexdeucher@gmail.com \
--cc=andresx7@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=ath10k@lists.infradead.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.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 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).