From: Paul Bolle <pebolle@tiscali.nl>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Michal Marek <mmarek@suse.cz>, Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: arm: pxa: CPU_PXA27x?
Date: Fri, 21 Nov 2014 11:43:47 +0100 [thread overview]
Message-ID: <1416566627.6958.16.camel@x220> (raw)
Robert,
Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Why is that select needed? For what it's worth: __cpu_is_pxa27x()
compiles to something interesting if CONFIG_PXA27x is defined.
In https://lkml.org/lkml/2014/9/30/578 I proposed a patch that emits a
warning in cases like this. Like _all_ Kconfig related patches I've seen
flying by lately it appears to be dropped in /dev/null. What's going on?
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: arm: pxa: CPU_PXA27x?
Date: Fri, 21 Nov 2014 11:43:47 +0100 [thread overview]
Message-ID: <1416566627.6958.16.camel@x220> (raw)
Robert,
Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Why is that select needed? For what it's worth: __cpu_is_pxa27x()
compiles to something interesting if CONFIG_PXA27x is defined.
In https://lkml.org/lkml/2014/9/30/578 I proposed a patch that emits a
warning in cases like this. Like _all_ Kconfig related patches I've seen
flying by lately it appears to be dropped in /dev/null. What's going on?
Paul Bolle
next reply other threads:[~2014-11-21 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 10:43 Paul Bolle [this message]
2014-11-21 10:43 ` arm: pxa: CPU_PXA27x? Paul Bolle
2014-11-21 16:48 ` Robert Jarzmik
2014-11-21 16:48 ` Robert Jarzmik
2014-11-21 17:09 ` Paul Bolle
2014-11-21 17:09 ` Paul Bolle
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=1416566627.6958.16.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mmarek@suse.cz \
--cc=robert.jarzmik@free.fr \
--cc=valentinrothberg@gmail.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.