From: patchwork-bot+netdevbpf@kernel.org
To: Tim Bird <Tim.Bird@sony.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.kernel.org, kuniyu@google.com,
mubashirq@google.com, willemb@google.com, dsahern@kernel.org,
pablo@netfilter.org, laforge@netfilter.org, fw@strlen.de,
ncardwell@google.com, ycheng@google.com, xemul@parallels.com,
idosch@mellanox.com, tim.bird@sony.com, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: Add SPDX ids to some source files
Date: Tue, 10 Mar 2026 01:40:05 +0000 [thread overview]
Message-ID: <177310680580.2015770.4327428961220043199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305004724.87469-1-tim.bird@sony.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Mar 2026 17:47:22 -0700 you wrote:
> Add SPDX-License-Identifier lines to several source
> files under the network sub-directory. Work on files
> in the core, dns_resolver, ipv4, ipv6 and
> netfilter sub-dirs. Remove boilerplate
> and license reference text to avoid ambiguity.
>
> Rusty Russell has expressed that his contributions
> were intended to be GPL-2.0-or-later.
>
> [...]
Here is the summary with links:
- net: Add SPDX ids to some source files
https://git.kernel.org/netdev/net-next/c/2ed4b46b4fc7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-10 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 0:47 [PATCH] net: Add SPDX ids to some source files Tim Bird
2026-03-10 1:40 ` patchwork-bot+netdevbpf [this message]
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=177310680580.2015770.4327428961220043199.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Tim.Bird@sony.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=idosch@mellanox.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=mubashirq@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.kernel.org \
--cc=pablo@netfilter.org \
--cc=willemb@google.com \
--cc=xemul@parallels.com \
--cc=ycheng@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.