Hi Gustavo, On Wed, Oct 31, 2012, Gustavo Padovan wrote: > > It is important that the monitor interface gets notified about > > a new device before its power on procedure has been started. > > > > For some reason that is no longer working as expected and the power > > on procedure runs first. It is safe to just notify about device > > registration and trigger the power on procedure afterwards. > > > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > > --- > > net/bluetooth/hci_core.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > Patch has been applied to bluetooth-next. Thanks. I guess you mean bluetooth.git? (that's where the patch is right now - not bluetooth-next). Also, I don't think the Cc: stable addition was necessary since this scheduling behavior seems to be something only introduced for 3.7 (not 100% sure about this though). Johan -- 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
