Hi Dave, > >> >> do you mind at least waiting for an ACK from my side. I haven't even > >> >> looked at the final patch. > >> > > >> > Sure, I haven't pushed it out yet, so now's your chance :) > >> > >> Grumble, I accidently pushed my net-2.6 queue out before you > >> had a chance to reply, sorry :-( > > > > not a big deal. Just have to send a cleanup patch. The patch itself is > > fine, but from a style perspective it is different than everything else > > in the Bluetooth subsystem and I would have liked to fix that before > > pushing it. I wait with that for 2.6.32 since it is not important. > > Marcel, could you publish the bluetooth subsystem coding style > somewhere? People including me are confused about it. I remembered I > asked it from you, but it is still not very clear for me. it is kernel coding style like everything else, but some variable naming should be consistent. And that is nothing that is published, that is something that has been done since Max wrote it. Check the rest of the code. > > The other Dave, please send patches to linux-bluetooth only and lets > > follow the normal path to get them merged into Linus' tree. Skipping > > bluetooth-2.6 is not an option. You have to use the same process than > > everybody else. > > Why linux-bluetooth only? IMHO there could be more people to comment > and review if I send patches to both lkml and subsystem mailing list. Lets me make this perfectly clear here. Bluetooth patches are sent to the linux-bluetooth mailing list. There is no need to send them to netdev and/or LKML at the same time. Stop this cross-posting. They don't get more review there anyway. I take care of sending them for net-2.6 inclusion if I feel that they are appropriate. Regards Marcel -- 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
