Hi Gustavo, On Fri, Jun 01, 2012, Gustavo Padovan wrote: > * Vinicius Costa Gomes <vinicius.gomes@xxxxxxxxxxxxx> [2012-05-31 22:53:39 -0300]: > > > Most probably a typo, the check should have been for BT_SK_DEFER_SETUP > > instead of BT_DEFER_SETUP (which right now only represents a socket > > option). > > > > Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@xxxxxxxxxxxxx> > > --- > > net/bluetooth/af_bluetooth.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Patch has been applied to bluetooth-next. thanks. This patch fixes accepting L2CAP and RFCOMM connections for sockets with defer setup enabled (i.e. pretty much *all* sockets we have). This is now broken in 3.5-rc1 so the patch should go with the highest priority to the upstream trees. Furthermore, you said you applied it to bluetooth-next but it's not there. What's going on? 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
