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
| ||
|
Date: Fri, 20 May 2011 02:50:22 +0100 From: Jamie Iles <jamie@...ieiles.com> To: H Hartley Sweeten <hartleys@...ionengravers.com> Cc: Sascha Hauer <s.hauer@...gutronix.de>, Shawn Guo <shawn.guo@...escale.com>, Linus Walleij <linus.walleij@...ricsson.com>, Jonas Aaberg <jonas.aberg@...ricsson.com>, Linus Walleij <linus.walleij@...aro.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Grant Likely <grant.likely@...retlab.ca>, Lee Jones <lee.jones@...aro.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Jamie Iles <jamie@...ieiles.com> Subject: Re: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio On Thu, May 19, 2011 at 04:18:56PM -0500, H Hartley Sweeten wrote: > On Thursday, May 19, 2011 12:12 PM, Sascha Hauer wrote: > > On Thu, May 19, 2011 at 09:56:32PM +0800, Shawn Guo wrote: > >> On Thu, May 19, 2011 at 02:21:27PM +0200, Linus Walleij wrote: > >>> On Thu, May 19, 2011 at 10:56 AM, Shawn Guo <shawn.guo@...escale.com> wrote: > >>> > >>>> I start working on moving mxs gpio (arch/arm/mach-mxs/gpio.c) into > >>>> driver/gpio, and I see the possibility to go a different approach > >>>> from U300 one posted here. > >>> > >>> I've tried to figure out what relation the mail has to the U300 driver > >>> but cannot find any, more than that it's moving a driver... Please > >>> start a new mail thread. > >>> > >> I will post mxs-gpio driver once I get it done. Then please review > >> the code and see the difference between mxs-gpio and u300-gpio, > >> though these hardwares have something in common. > > > > I'm pretty sure they have something in common and even more that *all* > > gpio drivers have something in common. I wonder if it really makes sense > > to move the gpio driver to drivers/gpio without creating a common > > mmio_gpio_chip beforehand. This can't be very hard. > > Jamie Iles (cc'ed) posted some patches that extended the basic_mmio_gpio > driver so that it could be used as a library by other gpio drivers. > > Jamie, could you re-post that series to the linux-arm-kernel list for > review? Grant has applied these patches but I've put them in a public branch if that's OK rather than reposting: git://github.com/jamieiles/linux-2.6-ji.git gpio Jamie -- 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/
Powered by blists - more mailing lists