From: patchwork-bot+bluetooth@kernel.org
To: Tim Bird <Tim.Bird@sony.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, jannh@google.com,
kuba@kernel.org, kiran.k@intel.com, chharry@chromium.org,
gustavo@padovan.org, prameela.j04cs@gmail.com, maxk@qualcomm.com,
tim.bird@sony.com, linux-bluetooth@vger.kernel.org,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: Add SPDX id lines to some source files
Date: Thu, 04 Jun 2026 19:30:04 +0000 [thread overview]
Message-ID: <178060140441.2988649.4114962772148712857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260604170633.730139-1-tim.bird@sony.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 4 Jun 2026 11:06:33 -0600 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: Add SPDX id lines to some source files
https://git.kernel.org/bluetooth/bluetooth-next/c/ae283ad45b1d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-04 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 17:06 [PATCH v3] Bluetooth: Add SPDX id lines to some source files Tim Bird
2026-06-04 18:42 ` [v3] " bluez.test.bot
2026-06-04 19:30 ` patchwork-bot+bluetooth [this message]
2026-06-05 10:21 ` [PATCH v3] " Paul Menzel
2026-06-05 16:25 ` Bird, Tim
2026-06-05 19:53 ` Luiz Augusto von Dentz
2026-06-05 20:31 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178060140441.2988649.4114962772148712857.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=Tim.Bird@sony.com \
--cc=chharry@chromium.org \
--cc=gustavo@padovan.org \
--cc=jannh@google.com \
--cc=kiran.k@intel.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=prameela.j04cs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox