From: Olof Johansson <olof@lixom.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Emilio Lopez <emilio@elopez.com.ar>,
torvalds@linux-foundation.org
Subject: Re: [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings
Date: Sat, 29 Jun 2013 16:20:38 -0700 [thread overview]
Message-ID: <20130629232038.GA12533@quad.lixom.net> (raw)
In-Reply-To: <20130629231425.GG3353@n2100.arm.linux.org.uk>
On Sun, Jun 30, 2013 at 12:14:26AM +0100, Russell King - ARM Linux wrote:
> On Sat, Jun 29, 2013 at 03:54:26PM -0700, Olof Johansson wrote:
> > Most of this ruffle seems to be about the fact that booting a kernel
> > with a device tree that doesn't conform to the brand spanking new,
> > and never previously enforced, binding for the cpu nodes will produce
> > a WARN_ON(). Lots of our in-tree device trees fall into this category.
> >
> > And while I think it was a bad idea for Lorenzo to ask for this to be
> > merged as a fix this late (and most in particular for stable), as far
> > as I can tell nothing (new) is broken by it -- just the alarming warning
> > is being printed.
> >
> > I think it probably makes sense to downgrade the WARN to just a printk, and
> > people will be a lot less worried. How about the below?
> >
> > If you're OK with it, Russell, can we get your ack so Linus can apply
> > directly given the imminence of final 3.10? Or, if you prefer, you can of
> > course apply and send it on instead.
>
> You can have my usual rmk+kernel ack for it with one change...
>
> > + if (!bootcpu_valid) {
> > + pr_warn("DT missing boot CPU MPIDR[23:0], fall back to "
> > + "default cpu_logical_map\n");
>
> Don't wrap messages kernel messages inspite of what checkpatch says.
> Always keep messages like that on a single line so they're greppable.
> Checkpatch is far from perfect and does get stuff wrong, and this is
> one of its common mistakes.
I didn't even run it through checkpatch, and I prefer greppable strings too --
I just went with what the rest of the file already used in this case to keep
the change minimal given timing.
I'll send a fresh copy with your ack and the above changed. Thanks.
-Olof
next prev parent reply other threads:[~2013-06-29 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:44 Maxime Ripard
2013-06-28 16:44 ` [PATCH 1/2] ARM: dts: sunxi: cpus/cpu nodes dts updates Maxime Ripard
2013-06-28 16:44 ` [PATCH 2/2] sunxi: a10s: dtsi: Convert cpu node to the new cpu bindings Maxime Ripard
2013-06-28 17:15 ` [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings Lorenzo Pieralisi
2013-06-28 20:03 ` Maxime Ripard
2013-06-28 20:05 ` Olof Johansson
2013-06-28 21:45 ` Lorenzo Pieralisi
2013-06-29 18:07 ` Maxime Ripard
2013-06-29 19:03 ` Lorenzo Pieralisi
2013-06-29 19:38 ` Russell King - ARM Linux
2013-06-29 20:11 ` Lorenzo Pieralisi
2013-06-29 22:54 ` Olof Johansson
2013-06-29 23:14 ` Russell King - ARM Linux
2013-06-29 23:20 ` Olof Johansson [this message]
2013-06-30 9:48 ` Lorenzo Pieralisi
2013-07-05 10:19 ` Lorenzo Pieralisi
2013-07-12 9:37 ` Maxime Ripard
2013-07-02 12:12 ` Nicolas Ferre
2013-07-02 12:56 ` Lorenzo Pieralisi
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=20130629232038.GA12533@quad.lixom.net \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=torvalds@linux-foundation.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®