From: Mark Brown <broonie@kernel.org>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the bpf tree
Date: Thu, 17 Sep 2026 12:09:57 +0100 [thread overview]
Message-ID: <66d3f5cd-12df-4000-8459-360ba57cea12@sirena.org.uk> (raw)
In-Reply-To: <DLHJEZ0K0FV1.SCQLJJQNS1ES@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Thu, Sep 17, 2026 at 12:59:30PM +0200, Kumar Kartikeya Dwivedi wrote:
> +To Eduard
>
> On Thu Sep 17, 2026 at 12:30 PM CEST, Mark Brown wrote:
> > Commits
> >
> > 4499609f99fd5 ("selftests/bpf: Test global subprog callback contexts")
> > 3506b9a2f1085 ("bpf: Verify global subprogs in each sleepability context")
> >
> > are missing a Signed-off-by from their committers
Does the contacts list for the BPF trees need to be updated?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-17 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 10:30 Missing signoff in the bpf tree Mark Brown
2026-09-17 10:59 ` Kumar Kartikeya Dwivedi
2026-09-17 11:09 ` Mark Brown [this message]
2026-09-17 11:20 ` Kumar Kartikeya Dwivedi
2026-09-17 11:23 ` Mark Brown
2026-09-17 11:27 ` Kumar Kartikeya Dwivedi
2026-09-17 15:03 ` Mark Brown
2026-09-17 17:08 ` Eduard Zingerman
2026-09-17 17:15 ` Mark Brown
2026-09-17 17:27 ` Andrii Nakryiko
2026-09-17 18:02 ` Eduard Zingerman
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=66d3f5cd-12df-4000-8459-360ba57cea12@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
/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