linux-kernel - RE: [PATCH 2/2] pinctrl: Pass name instead of device to pin_config

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: <74CDBE0F657A3D45AFBB94109FB122FF176BE92A7E@HQMAIL01.nvidia.com>
Date:	Mon, 19 Dec 2011 10:20:05 -0800
From:	Stephen Warren <swarren@...dia.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] pinctrl: Pass name instead of device to pin_config_*

Linus Walleij wrote at Sunday, December 18, 2011 3:27 PM:
> On Fri, Dec 16, 2011 at 12:57 AM, Stephen Warren <swarren@...dia.com> wrote:
> 
> > Obtaining a "struct pinctrl_dev *" is difficult for code not directly
> > related to the pinctrl subsystem. However, the device name of the pinctrl
> > device is fairly well known. So, modify pin_config_*() to take the device
> > name instead of the "struct pinctrl_dev *".
> >
> > Signed-off-by: Stephen Warren <swarren@...dia.com>
> 
> Thanks Stephen, excellent, both applied.
> 
> I had to fix it up a bit to match the other
> refactoring patch I made so check the result in my tree or -next.

Yes, I think that looks fine, thanks.

Thanks for fixing up the documentation for me too.

BTW, do you know which commits you're planning on you're planning on
sending to mainline during the next merge window? If it includes these
two patches, I may be able to convert Tegra over to using the new pinctrl
driver in 3.3. And is your for-next branch stable (i.e. never rebased)
so that the arm-soc tree can use it as a dependency for my patches?

-- 
nvpublic

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