[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=hN6NeLdXAjzeeYwcZR7+BoJ1BQg@mail.gmail.com>
Date: Sun, 15 May 2011 19:29:04 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Greg KH <greg@...ah.com>
Cc: Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@...ricsson.com>,
devel@...verdev.osuosl.org,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Par-Gunnar Hjalmdahl <pghatwork@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Vitaly Wool <vitalywool@...il.com>,
Marcel Holtmann <marcel@...tmann.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org,
Lukasz Rymanowski <Lukasz.Rymanowski@...to.com>,
linux-bluetooth@...r.kernel.org,
Pavan Savoy <pavan_savoy@...y.com>,
Lee Jones <lee.jones@...aro.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v6] Add ST-Ericsson CG2900 driver
2011/5/15 Greg KH <greg@...ah.com>:
> That's why you should only use staging as a last resort, not as your
> primary way of getting code into the kernel, especially for stuff with
> a constantly changing in-kernel interface like you have pointed out
> here.
Agree 100%
Trust me, we tried this already.
> Just do the "real work" first and get it merged the real way if at all
> possible.
This driver development has gone into statis due to conflicts and
endless discussions pertaining to the HCI transport layer
beneath it.
It was my recommendation to put it into staging, by doing this
people can talk about the architecture by submitting *patches*
to show how they want it instead of these fruitless discussions.
So this should be a case where staging really helps, at least in
my dreams.
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/
Powered by blists - more mailing lists