linux-kernel - Re: [patch 2.6.24-rc4-mm 0/6] gpiolib updates

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]

Date:	Mon, 10 Dec 2007 17:07:43 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	David Brownell <david-b@...bell.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	eric miao <eric.y.miao@...vell.com>
Subject: Re: [patch 2.6.24-rc4-mm 0/6] gpiolib updates

Hi David,

On Sun, 9 Dec 2007 20:34:59 -0800, David Brownell wrote:
> I'm thinking there should be a non-functional change to
> the gpiolib code:  move it from lib to drivers/gpio.
> 
> My question is whether that's better done by replacing
> the current patches with one new patch, or by a patch
> deleting the current lib/gpiolib.c and adding a new
> drivers/gpio/gpiolib.c ... I think the former would
> make more sense to anyone looking at GIT history.

If gpiolib isn't in git yet, then indeed updating the patch that
creates it before it goes in git sounds more sensible. Let's not make
the git history more complex than needed.

Thanks,
-- 
Jean Delvare
--
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/