linux-kernel - Re: [PATCH v2 0/2] Move Freescale MXS gpio driver into 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] [day] [month] [year] [list]

Message-ID: <20110603175723.GE15616@ponder.secretlab.ca>
Date:	Fri, 3 Jun 2011 11:57:23 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Sascha Hauer <s.hauer@...gutronix.de>
Cc:	Shawn Guo <shawn.guo@...aro.org>, linux-kernel@...r.kernel.org,
	arnd@...db.de, kernel@...gutronix.de,
	linux-arm-kernel@...ts.infradead.org, patches@...aro.org
Subject: Re: [PATCH v2 0/2] Move Freescale MXS gpio driver into drivers/gpio

On Mon, May 30, 2011 at 08:45:02AM +0200, Sascha Hauer wrote:
> Grant,
> 
> I suppose we should take this through the architecture tree. Can I have
> your Ack for this?
> 

Actually, as mentioned in my other email, I'd like to see this series
respun with a separate patch for just moving the gpio driver (without
breaking the build).  

Also, I've been thinking about how to merge these changes, and I'd
rather take them through the gpio tree since there will be a lot of
conflicts with the other gpio driver moves.  It will be easier to
resolve merge conflicts if I push it out to my tree and allow the
subarch trees to merge in mine if necessary.

g.
--
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/