All of lore.kernel.org
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: meson: MESON6_TIMER?
Date: Fri, 26 Sep 2014 14:15:00 +0200	[thread overview]
Message-ID: <1411733700.7866.29.camel@x220> (raw)

Hi Carlo,

Your commit 3b8f5030ddcf ("ARM: meson: add basic support for MesonX
SoCs") landed in next-20140926. It adds (among other things) a select
statement:
    select MESON6_TIMER

But there's no Kconfig symbol MESON6_TIMER (in next-20140926). I assume
that this symbol is queued somewhere. (Probably related is the currently
orphaned DT string "amlogic,meson6-timer".) Is that correct?


Paul Bolle

WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Carlo Caione <carlo@caione.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: ARM: meson: MESON6_TIMER?
Date: Fri, 26 Sep 2014 14:15:00 +0200	[thread overview]
Message-ID: <1411733700.7866.29.camel@x220> (raw)

Hi Carlo,

Your commit 3b8f5030ddcf ("ARM: meson: add basic support for MesonX
SoCs") landed in next-20140926. It adds (among other things) a select
statement:
    select MESON6_TIMER

But there's no Kconfig symbol MESON6_TIMER (in next-20140926). I assume
that this symbol is queued somewhere. (Probably related is the currently
orphaned DT string "amlogic,meson6-timer".) Is that correct?


Paul Bolle


             reply	other threads:[~2014-09-26 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 12:15 Paul Bolle [this message]
2014-09-26 12:15 ` ARM: meson: MESON6_TIMER? Paul Bolle
2014-09-26 12:21 ` Carlo Caione
2014-09-26 12:21   ` Carlo Caione
2014-09-26 12:24   ` Paul Bolle
2014-09-26 12:24     ` Paul Bolle
2014-09-26 12:30     ` Carlo Caione
2014-09-26 12:30       ` Carlo Caione

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