Hi Jakub,
>>>> bluetooth-next pull request for net-next:
>>>>
>>>> - Add support for MediaTek MT7922 and MT7921
>>>> - Enable support for AOSP extention in Qualcomm WCN399x and Realtek
>>>> 8822C/8852A.
>>>> - Add initial support for link quality and audio/codec offload.
>>>> - Rework of sockets sendmsg to avoid locking issues.
>>>> - Add vhci suspend/resume emulation.
>
>>> Commit 0b59e272f932 ("Bluetooth: reorganize functions from hci_sock_sendmsg()")
>>> committer Signed-off-by missing
>>> author email: penguin-kernel@xxxxxxxxxxxxxxxxxxx
>>> committer email: marcel@xxxxxxxxxxxx
>>> Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
>>> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
>>
>> I suspect those fixed and force pushed since I originally applied them
>> given them all have my sign-offs, is this a blocker though?
>
> I'm not an expert on SoB semantics so not sure if it's a deal breaker.
> Stephen's checker will definitely notice and send us warnings.
> I think it's worth the hassle to rebase and resubmit for 7 bad commits.
at some point, I had to fix one commit via git rebase —interactive. Looks like it
then made me committer for all commits. Originally Luiz applied all these patches
and my Signed-off-by should be in it.
I can fix this for sure and get the right committer back, I am just curious what
git rebase did here.
Regards
Marcel
