From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: linuxwifi <linuxwifi@intel.com>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"jprvita@gmail.com" <jprvita@gmail.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux@endlessm.com" <linux@endlessm.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jprvita@endlessm.com" <jprvita@endlessm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] iwlwifi: Demote messages about fw flags size to info
Date: Tue, 8 Aug 2017 08:21:09 +0000 [thread overview]
Message-ID: <1502180468.15969.140.camel@intel.com> (raw)
In-Reply-To: <20170803144728.32305-1-jprvita@endlessm.com>
On Thu, 2017-08-03 at 07:47 -0700, João Paulo Rechi Vita wrote:
> These messages are not reporting a real error, just the fact that the
> firmware knows about more flags than the driver.
>
> Currently these messages are presented to the user during boot if there
> is no bootsplash covering the console, even when booting the kernel with
> "quiet".
>
> Demoting it to the warn level helps having a clean boot process.
>
> Signed-off-by: João Paulo Rechi Vita <jprvita@endlessm.com>
> ---
>
> v2 changes:
> - Set to warn level instead of info
>
> v3 changes:
> - Fix commit message typo
Thanks, João Paulo! I pushed this to our internal tree and it will
eventually reach the mainline following our normal upstreaming process.
--
Cheers,
Luca.
prev parent reply other threads:[~2017-08-08 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 14:51 [PATCH] iwlwifi: Demote messages about fw flags size to info João Paulo Rechi Vita
2017-07-24 11:01 ` Coelho, Luciano
2017-08-01 22:58 ` João Paulo Rechi Vita
2017-08-02 4:46 ` Luca Coelho
2017-08-03 14:30 ` [PATCH v2] " João Paulo Rechi Vita
2017-08-03 14:36 ` David Laight
2017-08-03 14:47 ` [PATCH v3] " João Paulo Rechi Vita
2017-08-08 8:21 ` Coelho, Luciano [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=1502180468.15969.140.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=jprvita@endlessm.com \
--cc=jprvita@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=linuxwifi@intel.com \
--cc=netdev@vger.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).