[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABBYNZKJaD01+o8Tuh7AX7=3Hct_6YqzQcWWzDvOcRpRdPOizQ@mail.gmail.com>
Date: Mon, 4 Oct 2021 20:47:35 -0700
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: David Miller <davem@...emloft.net>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: pull request: bluetooth 2021-10-04
Hi Jakub,
On Mon, Oct 4, 2021 at 6:22 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Mon, 4 Oct 2021 15:21:46 -0700 Luiz Augusto von Dentz wrote:
> > bluetooth-next pull request for net-next:
> >
> > - Add support for MediaTek MT7922 and MT7921
> > - Add support for TP-Link UB500
> > - 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.
>
> Now it's flipped, it's complaining about Luiz being the committer
> but there's only a sign off from Marcel :(
I did have both sign-off, or are you saying Ive now become the
committer of other patches as well? Which means whoever rebases the
tree has to sign-off the entire set as well, I guess other trees does
better with this because they don't have multiple committer but once
you have that it is kind hard to maintain this rule of committer must
sign-off, shouldn't we actually just check if there is one sign-off by
one of the maintainers that shall be considered acceptable? Or perhaps
there is some documentation on the matter?
--
Luiz Augusto von Dentz
Powered by blists - more mailing lists