Kalle Valo <kvalo@xxxxxxxxxxxxxx> writes: > Kai Heng Feng <kai.heng.feng@xxxxxxxxxxxxx> writes: > >>> On Oct 3, 2018, at 5:10 PM, Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: >>> >>> Kai-Heng Feng <kai.heng.feng@xxxxxxxxxxxxx> writes: >>> >>>> To avoid the firmware loading race between Bluetooth and WiFi on Intel >>>> 8260, load firmware exclusively when BT_INTEL is enabled. >>>> >>>> Signed-off-by: Kai-Heng Feng <kai.heng.feng@xxxxxxxxxxxxx> >>> >>> Still the commit log tells nothing about the actual problem which makes >>> review impossible. >> >> Sorry for that. The first two patches [1] only sends to linux-bluetooth and LMKL. > > For a patchset like this you should CC linux-wireless for all patches, > otherwise people just get confused. And even more so as patch 3 seems to > depend on the other patches. > >> I don’t know what really happened at hardware/firmware level, but >> making btusb and iwlwifi load firmware sequentially can workaround the >> issue. > > We don't apply ugly workarounds without understanding the issue. > >> Matt Chen may be able to explain this issue with more detail. > > Then you need to work with Matt so that the issue is properly explained > in the commit log. linux-bluetooth was not CCed, adding that. -- Kalle Valo
