public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] char/rtc: replace blacklist with whitelist
Date: Sun, 1 May 2016 13:21:07 -0700	[thread overview]
Message-ID: <20160501202107.GA14269@kroah.com> (raw)
In-Reply-To: <1461786317-568103-1-git-send-email-arnd@arndb.de>

On Wed, Apr 27, 2016 at 09:45:01PM +0200, Arnd Bergmann wrote:
> Every new architecture has to add itself to the growing list of those
> that do not support the legacy PC RTC driver.
> 
> This replaces the long list of architectures that don't support it
> with a shorter list of those that do.
> 
> The list is taken from those architectures that have a non-empty
> asm/mc146818rtc.h header file and were not explicitly blacklisted
> or select RTC_LIB.
> 
> Alpha and Loongson64 can already choose between this driver and
> an rtc-class based one. mn10300 is actually the only architecture
> now that still requires this driver, and that should be fairly
> easy to change to use rtc-cmos if we want to kill off rtc.ko
> for good.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> This time I've trimmed down the whitelist even more, and separate
> the patch from the other ones that are now all about the GEN_RTC
> driver.

So this is safe to take on it's own and you are going to redo that
larger series?

confused,

greg k-h

  parent reply	other threads:[~2016-05-01 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 19:45 [PATCH v3] char/rtc: replace blacklist with whitelist Arnd Bergmann
2016-04-27 19:52 ` Geert Uytterhoeven
2016-04-27 20:00   ` Arnd Bergmann
2016-05-01 20:21 ` Greg Kroah-Hartman [this message]
2016-05-01 20:59   ` Arnd Bergmann

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=20160501202107.GA14269@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox