From: patchwork-bot+netdevbpf@kernel.org
To: Marco Vedovati <marco.vedovati@crowdstrike.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, yonghong.song@linux.dev,
gregkh@linuxfoundation.org, thomas.weissschuh@linutronix.de,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-open-source@crowdstrike.com
Subject: Re: [PATCH bpf-next] tools/include: Add Linux-syscall-note to uapi/linux/types.h
Date: Thu, 15 Oct 2026 08:00:04 +0000 [thread overview]
Message-ID: <179205120452.3257574.2106728768170589694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261014194516.3030362-1-marco.vedovati@crowdstrike.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 14 Oct 2026 21:45:16 +0200 you wrote:
> tools/include/uapi/linux/types.h is the only header under
> tools/include/uapi/linux/ whose SPDX identifier lacks the
> Linux-syscall-note exception.
>
> The file was originally added as
> tools/testing/selftests/bpf/include/uapi/linux/types.h by
> commit 0a5539f66133 ("bpf: Provide a linux/types.h override for bpf
> selftests.") without any license header. Then
> commit 579f1d926c66 ("selftests/bpf: fix broken build due to types.h")
> added type definitions copied from include/uapi/linux/types.h, which
> is licensed under GPL-2.0 WITH Linux-syscall-note.
>
> [...]
Here is the summary with links:
- [bpf-next] tools/include: Add Linux-syscall-note to uapi/linux/types.h
https://git.kernel.org/bpf/bpf-next/c/f5bffe9f098f
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-10-15 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 19:45 [PATCH bpf-next] tools/include: Add Linux-syscall-note to uapi/linux/types.h Marco Vedovati
2026-10-15 8:00 ` 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=179205120452.3257574.2106728768170589694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-spdx@vger.kernel.org \
--cc=marco.vedovati@crowdstrike.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=yonghong.song@linux.dev \
/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.