All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Mark Brown" <broonie@kernel.org>
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 13:20:11 +0200	[thread overview]
Message-ID: <DLHJUSTDSQ05.28VUGOV7YPS6V@gmail.com> (raw)
In-Reply-To: <66d3f5cd-12df-4000-8459-360ba57cea12@sirena.org.uk>

On Thu Sep 17, 2026 at 1:09 PM CEST, Mark Brown wrote:
> 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?

Well, he's the committer, so makes sense to put him in the recipients as well :).
Once he gets to this he can probably force push to correct it, I guess.

  reply	other threads:[~2026-09-17 11:20 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
2026-09-17 11:20     ` Kumar Kartikeya Dwivedi [this message]
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=DLHJUSTDSQ05.28VUGOV7YPS6V@gmail.com \
    --to=memxor@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=broonie@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.