linux-kernel - RE: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio

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

Message-ID: <0D753D10438DA54287A00B027084269764D26C443E@AUSP01VMBX24.collaborationhost.net>
Date:	Thu, 28 Apr 2011 12:41:38 -0500
From:	H Hartley Sweeten <hartleys@...ionengravers.com>
To:	Linus Walleij <linus.walleij@...aro.org>,
	Grant Likely <grant.likely@...retlab.ca>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Lee Jones <lee.jones@...aro.org>,
	Jonas Aaberg <jonas.aberg@...ricsson.com>
Subject: RE: [PATCH 02/10] mach-u300: rewrite gpio driver, move to
 drivers/gpio

On Thursday, April 28, 2011 12:08 AM, Linus Walleij wrote:
> 2011/4/27 H Hartley Sweeten <hartleys@...ionengravers.com>:
>> The Makefile should probably be reordered, either alphabetically
>> or grouped by type (arch/mmio/i2c/spi/pci/etc) and then
>> alphabetically in order to reduce merge conflicts.
>
> Yes, but if I do that in my patchset I will screw up Grants GPIO tree
> completely, so I prefer that Grant do this. And maybe after pulling
> in my GPIO consolidation tree to his in that case, so we don't get
> undesired collisions. So leaving this for the GPIO maintainer.

This comment was intended for the GPIO maintainer.  Sorry for any
confusion.

Regards,
Hartley--
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/