linux-kernel - Re: [PATCH v3] char/rtc: replace blacklist with whitelist

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4188502.OBRvQGansG@wuerfel>
Date:	Sun, 01 May 2016 22:59:20 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] char/rtc: replace blacklist with whitelist

On Sunday 01 May 2016 13:21:07 Greg Kroah-Hartman wrote:
> 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@...db.de>
> > Acked-by: Alexandre Belloni <alexandre.belloni@...e-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?

What I tried to say here is that this patch is now completely
independent from the longer series, please apply it directly.

	Arnd