linux-kernel - Re: [PATCH v7 0/6] Introduce External Connector Class (extcon)

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:	Wed, 28 Mar 2012 15:24:07 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	MyungJoo Ham <myungjoo.ham@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, NeilBrown <neilb@...e.de>,
	Randy Dunlap <rdunlap@...otime.net>,
	Mike Lockwood <lockwood@...roid.com>,
	Arve Hjønnevag <arve@...roid.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	John Stultz <john.stultz@...aro.org>,
	Joerg Roedel <joerg.roedel@....com>, cw00.choi@...sung.com
Subject: Re: [PATCH v7 0/6] Introduce External Connector Class (extcon)

On Wednesday 28 March 2012, Greg KH wrote:
> 
> On Wed, Mar 28, 2012 at 06:39:08PM +0900, MyungJoo Ham wrote:
> > Dear Arnd,
> > 
> > Could you please consider the EXTCON patchset for the current merge window?
> 
> Wait, no, the current merge window for new stuff closed a week or so
> before 3.3 came out.  This needs to be in linux-next before the merge
> window opens to ensure that things work properly there before it can be
> accepted into the mainline tree.
> 
> So this could go into 3.5 at the earliest.

Right. I'm also not convinced that arm-soc is the right place for this to
go, and I had not planned to add the patches there. Unfortunately I also
haven't followed the last few versions and will have to do at least one
more review round and Ack/Nak the interfaces. I should probably do that
once -rc1 is out, so please send me a reminder if you don't hear back from
me in time.

Any opinions on which tree this should go through? I could take it into
arm-soc, but it's not really ARM-only. Maybe having it go through the
staging tree would be better, leaving MyungJoo in charge afterwards.
I guess we should also add a MAINTAINERS entry for the new subsystem.

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