From: Luca Coelho <luca@coelho.fi>
To: "João Paulo Rechi Vita" <jprvita@endlessm.com>
Cc: 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>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux@endlessm.com" <linux@endlessm.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iwlwifi: Demote messages about fw flags size to info
Date: Wed, 02 Aug 2017 07:46:48 +0300 [thread overview]
Message-ID: <1501649208.2588.55.camel@coelho.fi> (raw)
In-Reply-To: <CAOcMMifW4mVPj1TVkzQPdvT0YO6p1DUObNinzWv2_ZtCbfk9Mg@mail.gmail.com>
Hi João Paulo,
On Tue, 2017-08-01 at 15:58 -0700, João Paulo Rechi Vita wrote:
> Hello Luca,
>
> On Mon, Jul 24, 2017 at 4:01 AM, Coelho, Luciano
> <luciano.coelho@intel.com> wrote:
> > On Fri, 2017-07-21 at 07:51 -0700, João Paulo Rechi Vita wrote:
>
> (...)
>
> > > Currently these messages are presented to the user during boot if there
> > > is no bootsplash covering the console, sometimes even if the boot splash
> > > is enabled but has not started yet by the time this message is shown.
> > >
>
> I should have provided another piece of information here: all of this
> happens even when booting with the 'quiet' kernel parameter.
Oh, okay, that's annoying.
> > This specific case is harmless, but I'd rather keep this message as an
> > error, because in other situations it could lead to unexpected
> > behavioir, so I prefer to keep it very visible.
> >
> >
>
> I see your point, and I understand the purpose of these messages. I'm
> wondering if perhaps having them at the warning level would give them
> enough visibility, while still keeping a clean boot process to the end
> user. If so, I can send an updated patch.
>
> Thanks for your reply and for pointing to the fix for the root cause
> of that message.
Sure, I agree it's better to make it use IWL_WARN(), which will generate
a dev_warn() instead of a dev_err().
--
Cheers,
Luca.
next prev parent reply other threads:[~2017-08-02 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 14:51 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 [this message]
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
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=1501649208.2588.55.camel@coelho.fi \
--to=luca@coelho.fi \
--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
all inboxes | Powered by JetHome®