linux-kernel - Re: [PATCH] pinctrl: resurrect verbose pinmux-pins

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: <CACRpkdYrj2ay=k2MgYOekQtcfbP9FiY5Rju8VznJHrxG81Y7SQ@mail.gmail.com>
Date:	Mon, 5 Mar 2012 11:15:32 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dia.com>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Barry Song <21cnbao@...il.com>,
	Shawn Guo <shawn.guo@...escale.com>,
	Thomas Abraham <thomas.abraham@...aro.org>,
	Dong Aisheng <dong.aisheng@...aro.org>,
	Rajendra Nayak <rajendra.nayak@...aro.org>,
	Haojian Zhuang <haojian.zhuang@...vell.com>
Subject: Re: [PATCH] pinctrl: resurrect verbose pinmux-pins

On Fri, Mar 2, 2012 at 7:24 PM, Stephen Warren <swarren@...dia.com> wrote:
> Stephen Warren wrote at Friday, March 02, 2012 10:41 AM:
>> Stephen Warren wrote at Friday, March 02, 2012 10:22 AM:
>> > Linus Walleij wrote at riday, March 02, 2012 9:31 AM:
>> > > From: Linus Walleij <linus.walleij@...aro.org>
>> > >
>> > > This reintroduces the verbosity in the pinmux-pins file, now this
>> > > file will list all pins, their names, owning device (and if it's
>> > > a hog) and also in applicable cases the function and group making
>> > > use of that pin right now.
>> > >
>> > > Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
>> >
>> > It'd be nice if we could defer this fix until after all the API rework,
>> > because it'll cause all kinds of conflicts otherwise.
>>
>> Oh, I see this patch is in your for-next branch already before I had a chance
>> to comment on it. I guess I'll have write a patch to convert the removed struct
>> type to char*s and rebase on top of it:-(

Mainly because I saw it as a regression fix.

> I take that back. Can we please drop this patch and I'll provide an
> equivalent in my API rework series?

Yeah no problem, if the rest of the v3 patch set is OK I'll just
remove that patch.

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/