From: Kalle Valo <kvalo@codeaurora.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
"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: Sun, 26 Jul 2020 21:11:25 +0300 [thread overview]
Message-ID: <87y2n6404y.fsf@codeaurora.org> (raw)
In-Reply-To: <20200726152642.GA913@ninjato> (Wolfram Sang's message of "Sun, 26 Jul 2020 17:26:42 +0200")
Wolfram Sang <wsa@kernel.org> writes:
> On Thu, Jun 25, 2020 at 06:52:10PM +0200, Wolfram Sang wrote:
>> 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>
>> ---
>
> Any input on this? Or people I should add to CC?
This was discussed on another thread:
https://lkml.kernel.org/r/87mu3magfp.fsf@tynnyri.adurom.net
Unless Intel folks object I'm planning to take this to
wireless-drivers-next.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-07-26 18:11 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 [this message]
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
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=87y2n6404y.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.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 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.