linux-kernel - [RFC 0/3] Removal of GENERIC

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-next>] [day] [month] [year] [list]

Date:	Sun, 17 Mar 2013 22:42:00 +0900
From:	Alexandre Courbot <gnurou@...il.com>
To:	Mike Frysinger <vapier@...too.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Ralf Baechle <ralf@...ux-mips.org>
Cc:	uclinux-dist-devel@...ckfin.uclinux.org,
	linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
	linux-mips@...ux-mips.org, gnurou@...il.com,
	Alexandre Courbot <acourbot@...dia.com>
Subject: [RFC 0/3] Removal of GENERIC_GPIO from architecture code

These three patches are from a larger set that aims at completely removing the 
GENERIC_GPIO option from platform code and config files as a first step towards 
his complete removal. After that, the use of the generic GPIO API would be 
provided through gpiolib. This series has already been discussed (see 
https://lkml.org/lkml/2013/3/12/167 for details and the rationale between these 
patches) and approved by most architectures, but before having it rolled on 
linux-next I'd like to hear from the 3 following architectures which have not 
replied to the previous patch set and are the most likely to be affected by 
this (other architectures almost all require gpiolib to start with).

mips: pnx833x: used to select GENERIC_GPIO but I'm not sure if it's needed at 
all. I could not find a GPIO driver implementation that did not depend on 
gpiolib. Platform code is sometimes subtle though, so it is possible that I 
just missed it.

m68k: coldfire: turns gpiolib from optional to mandatory. Might increase the 
kernels size by ~15KB for builds that did not make use of gpiolib (are there 
still such builds?)

blackfin: turns gpiolib from optional to mandatory, same side-effect.

Note that all architectures *can* operate with gpiolib, but only the three 
above leave the option to not do so. Since a new GPIO API is being prepared 
around gpiolib amongst other features, the option of only supporting 
GENERIC_GPIO leads to fragmentation and a lot of confusion for both drivers and 
platform code.

If you have any good reason to not see these changes applied, please let me 
know shortly - acks are welcome too.

Thanks,
Alex.

Alexandre Courbot (3):
  mips: pnx833x: remove requirement for GENERIC_GPIO
  m68k: coldfire: use gpiolib
  blackfin: force use of gpiolib

 arch/blackfin/Kconfig | 4 ++--
 arch/m68k/Kconfig.cpu | 3 +--
 arch/mips/Kconfig     | 1 -
 3 files changed, 3 insertions(+), 5 deletions(-)

-- 
1.8.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/