Return-Path: MIME-Version: 1.0 Sender: linus.ml.walleij@gmail.com In-Reply-To: <20110515163257.GE1315@kroah.com> References: <1305040215-712-1-git-send-email-par-gunnar.p.hjalmdahl@stericsson.com> <20110515163257.GE1315@kroah.com> Date: Sun, 15 May 2011 19:29:04 +0200 Message-ID: Subject: Re: [PATCH v6] Add ST-Ericsson CG2900 driver From: Linus Walleij To: Greg KH Cc: Par-Gunnar Hjalmdahl , devel@driverdev.osuosl.org, Mathieu Poirier , Par-Gunnar Hjalmdahl , Arnd Bergmann , Vitaly Wool , Marcel Holtmann , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Lukasz Rymanowski , linux-bluetooth@vger.kernel.org, Pavan Savoy , Lee Jones , Alan Cox Content-Type: text/plain; charset=ISO-8859-1 List-ID: 2011/5/15 Greg KH : > 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