From: Paul Bolle <pebolle@tiscali.nl>
To: Barry Song <Baohua.Song@csr.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: clocksource: marco: CONFIG_ARCH_ATLAS7?
Date: Wed, 14 Jan 2015 09:51:56 +0100 [thread overview]
Message-ID: <1421225516.15397.41.camel@x220> (raw)
Barry,
Your commit 81428bbe1d8a ("clocksource: marco: Rename marco to atlas7")
is included in today's linux-next (ie, next-20150114). I noticed because
a script I use to check linux-next spotted a problem.
See, your commit renames one reference to CONFIG_ARCH_MARCO to
CONFIG_ARCH_ATLAS7. But there's no Kconfig symbol ARCH_ATLAS7 in
linux-next yet. I assume that one or more patches to add ARCH_ATLAS7 (or
to rename ARCH_MARCO to ARCH_ATLAS7) are queued somewhere. Is that
correct?
Paul Bolle
next reply other threads:[~2015-01-14 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 8:51 Paul Bolle [this message]
2015-01-14 9:21 ` clocksource: marco: CONFIG_ARCH_ATLAS7? Barry Song
2015-01-14 9:28 ` 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=1421225516.15397.41.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=Baohua.Song@csr.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=valentinrothberg@gmail.com \
/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