From: Paul Bolle <pebolle@tiscali.nl>
To: Hans Ulli Kroll <ulli.kroll@googlemail.com>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/1] RTC:driver for Cortina's SOC
Date: Tue, 12 May 2015 11:05:34 +0200 [thread overview]
Message-ID: <1431421534.2398.147.camel@x220> (raw)
In-Reply-To: <1431361537-10473-2-git-send-email-ulli.kroll@googlemail.com>
On Mon, 2015-05-11 at 18:25 +0200, Hans Ulli Kroll wrote:
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> +config RTC_DRV_GEMINI
> + tristate "Gemini SoC RTC"
> + help
> + If you say Y here you will get support for the
> + RTC found on Gemini SoC's.
> +
> + This driver can also be built as a module. If so, the module
> + will be called rtc-gemini.
This has, by the look of it, very little dependencies, probably just
RTC_CLASS. So I think that this symbol can be enabled in allyesconfig,
allmodconfig, and randconfig for most architectures. (I just tested this
- what a novel idea! - and it will indeed be set by allyesconfig and
allmodconfig on x86_64.)
> --- /dev/null
> +++ b/drivers/rtc/rtc-gemini.c
> +#include <mach/hardware.h>
Except for arm, builds using a .config containing
CONFIG_RTC_DRV_GEMINI=[my]
will fail here. (*/mach/hardware.h is mainly used for arm.) That is
bound to generate, well, fanmail for you. Perhaps it's better if
RTC_DRV_GEMINI depends on, say, ARCH_GEMINI.
Paul Bolle
next prev parent reply other threads:[~2015-05-12 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 16:25 [PATCHv2] " Hans Ulli Kroll
2015-05-11 16:25 ` [PATCHv2 1/1] " Hans Ulli Kroll
2015-05-12 9:05 ` Paul Bolle [this message]
2015-05-12 9:28 ` Arnd Bergmann
2015-05-13 18:23 ` Hans Ulli Kroll
2015-05-13 19:03 ` Arnd Bergmann
2015-05-13 19:05 ` Arnd Bergmann
2015-05-12 9:17 ` [PATCHv2] " Alexandre Belloni
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=1431421534.2398.147.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ulli.kroll@googlemail.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
Powered by JetHome