Hi Hans,
>> It is no longer possible to build BT_HCIUART into the kernel
>> when SERIAL_DEV_BUS is a loadable module, even if none of the
>> SERIAL_DEV_BUS based implementations are selected:
>> drivers/bluetooth/hci_ldisc.o: In function `hci_uart_set_flow_control':
>> hci_ldisc.c:(.text+0xb40): undefined reference to `serdev_device_set_flow_control'
>> hci_ldisc.c:(.text+0xb5c): undefined reference to `serdev_device_set_tiocm'
>> This adds a dependency to avoid the broken configuration.
>> Fixes: 7841d554809b ("Bluetooth: hci_uart_set_flow_control: Fix NULL deref when using serdev")
>> Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx>
>
> Another one I have on my TODO after the buildbot errors. In this case
> I do not believe this is the proper fix though.
>
> As pointed out in another thread discussing the series introducing
> this problem, hci_ldisc.c really should not depend on serdev,
> so the proper fix would be to have hci_bcm.c directly call
> the serdev flowcontrol and rts functions when the hci is
> backed by a serdev device, like hci_bcm.c is already doing
> when setting the baudrate, see host_set_baudrate in hci_bcm.c,
> so a similar host_set_flow_control should be added after which
> the changes to hci_ldisc.c can be reverted.
>
> If I understood Marcel correctly he prefers a single patch
> fixing this which also removes the changes from hci_ldisc.c,
> rather then a separate revert.
actually two patches is fine, but I want them as a patch series so they are applied in a row. I think best is first to revert the btusb.c changes and then apply the new ACPI PNP id.
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
