From: Luciano Coelho <luciano.coelho@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>, Wolfram Sang <wsa@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@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: Mon, 27 Jul 2020 09:21:52 +0300 [thread overview]
Message-ID: <8c5eadd1b400cf749a6ece07fedd7ce2a877bcdb.camel@intel.com> (raw)
In-Reply-To: <87y2n6404y.fsf@codeaurora.org>
On Sun, 2020-07-26 at 21:11 +0300, Kalle Valo wrote:
> 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.
Yes, please, just go ahead and take it. I have the same change in our
internal tree, but I didn't have the time to send it out due to my
vacations (from which I'm now back).
--
Cheers,
Luca.
next prev parent reply other threads:[~2020-07-27 6:22 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 [this message]
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=8c5eadd1b400cf749a6ece07fedd7ce2a877bcdb.camel@intel.com \
--to=luciano.coelho@intel.com \
--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=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).