linux-kernel - Re: [PATCH] staging: Add ST-Ericsson CG2900 driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdb+=RNMzRzWkruZLsq9rtr=2x3vC2DFz9dh5MoybkLLAw@mail.gmail.com>
Date:	Tue, 23 Oct 2012 10:48:19 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Nitin DHINGRA <nitin.dhingra@...ricsson.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	Anurag GUPTA-1 <anurag.gupta@...ricsson.com>,
	Ingvar PALSSON <ingvar.palsson@...ricsson.com>,
	Linus WALLEIJ <linus.walleij@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Par-Gunnar HJALMDAHL <par-gunnar.hjalmdahl@...ricsson.com>,
	Mridul JAIN <mridul.jain@...ricsson.com>
Subject: Re: [PATCH] staging: Add ST-Ericsson CG2900 driver

On Mon, Oct 22, 2012 at 8:37 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Thu, Oct 18, 2012 at 01:56:00PM +0200, Nitin DHINGRA wrote:
>> > Please refresh my memory, why is this going into drivers/staging/ and
>> > not into the "real" part of the kernel?
>> Putting the code in staging would be convenient so that if there are
>> any design/code suggestions it would be easier to incorporate.
>
> I don't understand.  Have you not tried to submit this code to the
> correct location already?  If not, why not?  If so, what was the result
> of the submission?

That was done by Par-Gunnar some year or two ago.

The reason to why it is being submitted to staging FTM is
that consensus on the transport mechanism over HCI could not be
reached during the patch review.

So my suggestion was to apply it in staging so that these who
want to change that mechanism can show in patches how they
want it to work going forward.

The TODO should include an item such as this:

- Reach consensus on the HCI transport abstraction

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/