Hi Padovan : > > > > > I would say something similar in style > > > > > to what I have done for the older CSR chips. See workaround above. > > > > > And on that note, you could use data->udev to get the usb_device > > > > > struct ;) > > > > As to this point, since now we are not using the btusb to download the > > > patch and radio table, > > > > I think we do not need to alloc the data struct and use data->udev > before > > > the workaround. > > > > So I'll still keep it was. How do you think it ? > > > > > > No, there is no extra allocation. data->udev is already there. Just use it as > > > Marcel said. > > > > There is somehow different with the older CSR chips. > > We need to return -NODEV directly if the bcd version of the 3012 chip is > lower or equal to 0x0001, > > And I think in such "return -NODEV" case, we totally do not need to alloc > the btusb_data. > > Ah yes, you right, I misread the patch. > I have re-sent the patch to the mail list. Btw, I changed the subject of the PATCH to make it be less than 60 characters. Thanks, Padovan, Steven, -- 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
