linux-kernel - Re: [PATCH] drivers: create a pinmux subsystem v2

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: <BANLkTikeY5QVpEa8uXckcFGvUf7Lg1PviA@mail.gmail.com>
Date:	Thu, 19 May 2011 19:38:22 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dia.com>
Cc:	Russell King <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Joe Perches <joe@...ches.com>,
	Martin Persson <martin.persson@...ricsson.com>,
	Lee Jones <lee.jones@...aro.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] drivers: create a pinmux subsystem v2

2011/5/19 Stephen Warren <swarren@...dia.com>:

> Still, if I was writing the patches, and I agreed with the above change,
> I think I'd want to put it into the first patchset (or at least before
> other people started implementing their pinmux drivers on top of the code)
> since it'd avoid everyone else (or me) having to refactor all their
> drivers almost immediately after writing them, plus it looks like a very
> simple change to the current pinmux patchset.

You're right and Sascha said the same thing, so I will includ it
in v3. I expect an Acked-by: in return ;-)

Yours,
Linus Walleij
--
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/