From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
tony.luck@intel.com, geert@linux-m68k.org, jejb@parisc-linux.org,
deller@gmx.de, benh@kernel.crashing.org, mpe@ellerman.id.au,
dalias@libc.org, dhowells@redhat.com,
yasutake.koichi@jp.panasonic.com, rth@twiddle.net,
ink@jurassic.park.msu.ru, linux-alpha@vger.kernel.org,
x86@kernel.org, a.zummo@towertech.it,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-sh@vger.kernel.org, rtc-linux@googlegroups.com,
linux-arch@vger.kernel.org
Subject: Re: char: legacy RTC cleanups
Date: Wed, 27 Apr 2016 09:44:10 +0000 [thread overview]
Message-ID: <20160427094410.GJ3264@piout.net> (raw)
In-Reply-To: <1461707052-1337718-1-git-send-email-arnd@arndb.de>
On 26/04/2016 at 23:44:04 +0200, Arnd Bergmann wrote :
> I've had these patches in my tree for a while, after the first one
> had a few issues that are fixed in this new version. The old-style
> PC RTC driver is now also disabled on m68k (as pointed out by
> Geert), ppc (it was also blacklisted), and m32r (I showed that
> it did not build).
>
> For the genrtc driver, rearranging the headers makes it simpler
> to use and reduces duplication. In case of alpha and mn10300,
> I've shown that the genrtc and rtc drivers are doing the same
> thing, so we don't need them both. The remaining three
> architectures (m68k, parisc, powerpc) actually all support
> the newer rtc-generic driver, so we could remove genrtc completely
> if we want to.
>
Personally, I'd go for the kill and remove genrtc instead of cleaning it
up.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-27 9:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 21:44 char: legacy RTC cleanups Arnd Bergmann
2016-04-26 21:44 ` [PATCH 1/8] char/rtc: replace blacklist with whitelist Arnd Bergmann
2016-04-27 8:31 ` Alexandre Belloni
2016-04-26 21:44 ` [PATCH 2/8] char/rtc: legacy RTC is no longer supported on x86 Arnd Bergmann
2016-04-27 8:35 ` Alexandre Belloni
2016-04-27 10:05 ` Thomas Gleixner
2016-04-26 21:44 ` [PATCH 3/8] char/rtc: remove empty asm/mc146818rtc.h files Arnd Bergmann
2016-04-27 8:41 ` Alexandre Belloni
2016-04-26 21:44 ` [PATCH 4/8] char/rtc: move mc146818rtc code out of asm-generic/rtc.h Arnd Bergmann
2016-04-27 9:29 ` Alexandre Belloni
2016-04-27 9:59 ` Arnd Bergmann
2016-04-26 21:44 ` [PATCH 5/8] char/genrtc: powerpc: use asm-generic/rtc.h Arnd Bergmann
2016-04-26 21:44 ` [PATCH 6/8] char/genrtc: parisc: " Arnd Bergmann
2016-04-26 22:07 ` Rolf Eike Beer
2016-04-27 11:21 ` Arnd Bergmann
2016-04-27 11:35 ` Arnd Bergmann
2016-04-27 11:55 ` Geert Uytterhoeven
2016-04-27 12:44 ` Arnd Bergmann
2016-04-26 21:44 ` [PATCH 7/8] char/genrtc: disallow building on Alpha Arnd Bergmann
2016-04-26 21:44 ` [PATCH 8/8] char/genrtc: disallow building on mn10300 Arnd Bergmann
2016-04-27 7:54 ` char: legacy RTC cleanups Geert Uytterhoeven
2016-04-27 8:33 ` Arnd Bergmann
2016-04-27 8:41 ` Geert Uytterhoeven
2016-04-27 9:44 ` Alexandre Belloni [this message]
2016-04-27 10:07 ` Arnd Bergmann
2016-04-27 10:19 ` Geert Uytterhoeven
2016-04-27 11:30 ` 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=20160427094410.GJ3264@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=dalias@libc.org \
--cc=deller@gmx.de \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jejb@parisc-linux.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rtc-linux@googlegroups.com \
--cc=rth@twiddle.net \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yasutake.koichi@jp.panasonic.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;
as well as URLs for NNTP newsgroup(s).