linux-kernel - Re: [PATCH v2] MAINTAINERS: add a sub-entry for the Qualcomm bluetooth driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMRc=Md0FCfqAxqLN98QbMFeACbq8DU6o9k6j+bnF6jPY=KGdQ@mail.gmail.com>
Date: Fri, 11 Jul 2025 15:45:55 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>, 
	Luiz Augusto von Dentz <luiz.von.dentz@...el.com>, Jeff Johnson <jeff.johnson@....qualcomm.com>, 
	Shuai Zhang <quic_shuaz@...cinc.com>, Stephan Gerhold <stephan.gerhold@...aro.org>, 
	Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, linux-bluetooth@...r.kernel.org, 
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH v2] MAINTAINERS: add a sub-entry for the Qualcomm
 bluetooth driver

On Fri, Jul 11, 2025 at 3:42 PM Luiz Augusto von Dentz
<luiz.dentz@...il.com> wrote:
>
> Hi Bartosz,
>
> On Thu, Jul 10, 2025 at 10:22 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> >
> > On Wed, Jul 9, 2025 at 7:06 PM Konrad Dybcio
> > <konrad.dybcio@....qualcomm.com> wrote:
> > >
> > > On 7/9/25 4:47 PM, Bartosz Golaszewski wrote:
> > > > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> > > >
> > > > Patches modifying drivers/bluetooth/hci_qca.c should be Cc'ed to the
> > > > linux-arm-msm mailing list so that Qualcomm maintainers and reviewers
> > > > can get notified about proposed changes to it. Add a sub-entry that adds
> > > > the mailing list to the list of addresses returned by get_maintainer.pl.
>
> Should this go via bluetooth-next or arm-msm has its own dedicated
> tree? If we continue using bluetooth-next let's agree to have someone
> from linux-arm-msm signing-off the patches for these drivers before we
> merge them in bluetooth-next, including this change.
>

I think this should go through bluetooth-next. Let's wait for Konrad
or Bjorn to Ack this then.

Bart