Re: [PATCH v2] Bluetooth: Add SPDX id lines to some source files

Luiz Augusto von Dentz <[email protected]> Thu, 4 Jun 2026 12:53:45 -0400
Newsgroups org.kernel.vger.linux-spdx,org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-kernel
Message-ID <CABBYNZKv=+atEF6Ko6Zs=uc+KtK+4xq2Ak_Re4H8jA45gkwtdA@mail.gmail.com>
Hi Tim,

On Thu, Jun 4, 2026 at 12:41=E2=80=AFPM Bird, Tim <[email protected]> wrote=
:
>
>
>
> > -----Original Message-----
> > From: Luiz Augusto von Dentz <[email protected]>
> > Hi Tim,
> >
> > On Wed, Jun 3, 2026 at 8:44=E2=80=AFPM Tim Bird <[email protected]> wro=
te:
> > >
> > > Many bluetooth source files are missing SPDX-License-Identifier
> > > lines. Add appropriate IDs to these files, and remove other
> > > license lines from the headers.
> > >
> > > Leave the warranty disclaimer in files where the license ID is
> > > GPL-2.0 but the wording of the disclaimer is slightly different
> > > from that of the GPL v2 disclaimer.
> > >
> > > It is not different enough to cause licensing conflicts, but is
> > > kept to honor the original contributors' legal intent.
> > >
> > > ---
> > > V1 -> V2:
> > >  - Leave different warranty disclaimers (which is most them)
> > >  - Remove files recently removed from drivers/bluetooth from the patc=
h
> > >
> > > Signed-off-by: Tim Bird <[email protected]>
> >
> > `git am` doesn't pick up your Signed-off-by because it is after ---`,
> > it seems to be considered a comment.
>
> Ah crud!!  What a dumb mistake on my part.
> Thanks for the heads up.
>
> Should I send a v3 to fix this?

I can readd it manually if you are not planning a v3 to address other comme=
nts.

--=20
Luiz Augusto von Dentz