From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Wolfram Sang <wsa@kernel.org>, linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] iwlwifi: yoyo: don't print failure if debug firmware is missing
Date: Thu, 26 Nov 2020 14:27:16 +0100 [thread overview]
Message-ID: <b500e3f5-6ac7-a96e-bcb9-6fd30f3c5fe0@molgen.mpg.de> (raw)
In-Reply-To: <20200625165210.14904-1-wsa@kernel.org>
[Sorry, I did not know where and how to import the thread, and only got
the first message from Patchwork.]
Dear Linux folks,
Am 25.06.20 um 18:52 schrieb Wolfram Sang:
> Missing this firmware is not fatal, my wifi card still works. Even more,
> I couldn't find any documentation what it is or where to get it. So, I
> don't think the users should be notified if it is missing. If you browse
> the net, you see the message is present is in quite some logs. Better
> remove it.
>
> Signed-off-by: Wolfram Sang <wsa@kernel.org>
> ---
>
> This is only build tested because I wanted to get your opinions first. I
> couldn't find any explanation about yoyo, so I am entering unknown
> territory here.
[…]
Despite commit 3f4600de8c93 (iwlwifi: yoyo: don't print failure if debug
firmware is missing) being in Linux since version 5.9-rc1, I am still
seeing this with Debian’s Linux 5.9.9.
Kind regards,
Paul
prev parent reply other threads:[~2020-11-26 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 16:52 [RFC PATCH] iwlwifi: yoyo: don't print failure if debug firmware is missing Wolfram Sang
2020-07-26 15:26 ` Wolfram Sang
2020-07-26 18:11 ` Kalle Valo
2020-07-26 18:24 ` Wolfram Sang
2020-07-27 6:21 ` Luciano Coelho
2020-08-02 15:08 ` Kalle Valo
2020-11-26 13:27 ` Paul Menzel [this message]
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=b500e3f5-6ac7-a96e-bcb9-6fd30f3c5fe0@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.org \
--cc=wsa@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).