public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Barry Song <Barry.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" <linux-kernel@vger.kernel.org>
Subject: Re: clocksource: marco: CONFIG_ARCH_ATLAS7?
Date: Wed, 14 Jan 2015 10:28:58 +0100	[thread overview]
Message-ID: <1421227738.15397.46.camel@x220> (raw)
In-Reply-To: <5EB3BFCD089AD643B9BB63439F5FD5E90177A62F01@SHAASIEXM01.ASIA.ROOT.PRI>

On Wed, 2015-01-14 at 09:21 +0000, Barry Song wrote:
> > -----Original Message----- 
> > 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?
> > 
> Yes, paul.
> It is queuing in arm-soc for refining my pull-request. Related patches
> have been acked by Arnd.

Unless the related patches take a long time to land (say, until after
v3.20-rc1) I won't bother you again about this.

Thanks!


Paul Bolle


      reply	other threads:[~2015-01-14  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  8:51 clocksource: marco: CONFIG_ARCH_ATLAS7? Paul Bolle
2015-01-14  9:21 ` Barry Song
2015-01-14  9:28   ` Paul Bolle [this message]

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=1421227738.15397.46.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=Barry.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