From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: smp: Remove CPU: shutdown notice
Date: Wed, 18 Jan 2017 22:39:48 +0000 [thread overview]
Message-ID: <20170118223948.GR27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <fd4a4f48-f19e-dcac-c286-8e03db89e99a@gmail.com>
On Tue, Jan 17, 2017 at 03:39:45PM -0800, Florian Fainelli wrote:
> Well, for one it's inconsistent, and it also leaves room for subtle
> timing/caching issues with some platforms (OK, maybe not so much).
> Improving the speed and consistency was the primary motive.
Actually, it's not as inconsistent as you claim.
c68b0274fb3c ("ARM: reduce "Booted secondary processor" message to debug level")
dropped the corresponding pr_info() in the bringup path to debug level,
so to be consistent, this one should be dropped to debug level too.
Removing it arguably makes it more inconsistent!
So, I'd be willing to accept a patch lowering this to a pr_debug()
to make it more consistent with the bringup path, but otherwise the
consistency argument doesn't really stand.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-01-18 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 23:07 [PATCH] ARM: smp: Remove CPU: shutdown notice Florian Fainelli
2017-01-17 23:23 ` Russell King - ARM Linux
2017-01-17 23:39 ` Florian Fainelli
2017-01-18 9:55 ` Petr Mladek
2017-01-18 19:56 ` Florian Fainelli
2017-01-19 12:07 ` Sergey Senozhatsky
2017-01-18 22:39 ` Russell King - ARM Linux [this message]
2017-01-18 22:49 ` Florian Fainelli
2017-01-18 22:53 ` [PATCH] ARM: Reduce "CPU: shutdown" message to debug level Florian Fainelli
2017-01-18 23:20 ` Russell King - ARM Linux
2017-01-19 0:27 ` Florian Fainelli
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=20170118223948.GR27312@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).