Hi Marcel, On Sun, Sep 14, 2014, Marcel Holtmann wrote: > The Bluetooth core already does processing of the HCI command header > and puts it together before sending it to the driver. It is not really > efficient for the driver to look at the HCI command header again in > case it has to make certain decisions about certain commands. To make > this easier, just provide the opcode as part of the SKB control buffer > information. The extra information about the opcode is optional and > only provided for HCI commands. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > include/net/bluetooth/bluetooth.h | 1 + > net/bluetooth/hci_core.c | 1 + > 2 files changed, 2 insertions(+) Applied to bluetooth-next. Thanks. 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
