linux-kernel - RE: [PATCH 0/3] pinctrl: move the core per-device handlers to core

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]

Date:	Mon, 13 Feb 2012 12:01:14 -0800
From:	Stephen Warren <swarren@...dia.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Olof Johansson <olof@...om.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	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>,
	Barry Song <21cnbao@...il.com>,
	Tony Lindgren <tony@...mide.com>
Subject: RE: [PATCH 0/3] pinctrl: move the core per-device handlers to core

Linus Walleij wrote at Monday, February 13, 2012 12:48 PM:
> On Sat, Feb 11, 2012 at 7:18 AM, Stephen Warren <swarren@...dia.com> wrote:
> 
> > I'll probably want to rework the 3 patches your changes break anyway (in
> > order to completely remove use of board-*-pinmux.c when booting from DT,
> > once I write the DT code) and so you may as well not apply them, just
> > the driver itself. It'll save some churn.
> 
> OK will that happen for this merge window or is the driver going to sit
> unused for the 3.4 cycle?
> 
> I'm mainly thinking if the underlying driver may be subject to change I
> could just keep it out-of-tree, unless you want it merged in for some
> practical reason, then I'll just merge it.

IIRC, people hoped that the common pinctrl bindings would make it into
3.4. If that happens, the driver won't be unused in 3.4.

I don't foresee any changes to the driver except those driven by any
changes to the core pinctrl itself, so I don't foresee any need to keep
it out of tree.

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