2011/5/15 Greg KH <greg@xxxxxxxxx>: > 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-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
