On Sun, 2014-12-14 at 11:40 +0100, Pavel Machek wrote: > On Sun 2014-12-14 00:30:13, Marcel Holtmann wrote: > > Hi Pavel, > > > > > Add hci_h4p bluetooth driver to staging tree. This device is used > > > for example on Nokia N900 cell phone. > > > > > > Signed-off-by: Pavel Machek <pavel@xxxxxx> > > > Thanks-to: Sebastian Reichel <sre@xxxxxxxxxx> > > > Thanks-to: Joe Perches <joe@xxxxxxxxxxx> > > > > > > --- > > > > > > > > > I'd prefer to resurect the driver in staging/ in order not to lose > > > history, but Marcel wanted to treat it as new submission, so I'm doing > > > that. > > > > that history is in linux.git now for all times. No need to repeat it. I rather not play around with that again. Lets get a minimal driver merged so we can give people something to improve. > > > > We will merge minimum version. Still I'd like complete history for > credits and bisect and easy ability to diff original and minimum > version. FWIW, I found that developing the driver outside of the main kernel tree for merge is the best way to keep a history that's not too interesting in the kernel tree. Something like: https://github.com/hadess/gt9xx will allow small reversible commits, make it easy to branch for testing (say a bug crops up, create a branch, fix the bug, get somebody to test it, merge to master, and copy/paste the files to the upstream git tree for inclusion). Of course, in your case you might need to create a backport for the whole bluetooth sub-system, as it uses internal API, which makes it harder. But it's still viable for large cleanups, and pre-merge changes while keeping history. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
