From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the bpf-next tree
Date: Wed, 14 Aug 2024 08:53:19 +1000 [thread overview]
Message-ID: <20240814085319.719b42ff@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hi all,
Commits
e811c1ee15c7 ("bpf: convert bpf_token_create() to CLASS(fd, ...)")
795bc52f75ad ("bpf: more trivial fdget() conversions")
139dc6fa791d ("bpf: trivial conversions for fdget()")
2d74d8e9897c ("bpf: switch maps to CLASS(fd, ...)")
b57c48f806fd ("bpf: switch fdget_raw() uses to CLASS(fd_raw, ...)")
b7014005e1e8 ("bpf: convert __bpf_prog_get() to CLASS(fd, ...)")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-08-13 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 22:53 Stephen Rothwell [this message]
2024-08-13 22:57 ` linux-next: Signed-off-by missing for commit in the bpf-next tree Andrii Nakryiko
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 21:00 Stephen Rothwell
2024-11-11 16:24 ` Andrii Nakryiko
2023-12-07 21:47 Stephen Rothwell
2023-12-07 21:57 ` Andrii Nakryiko
2022-11-22 21:24 Stephen Rothwell
2022-11-22 21:35 ` Alexei Starovoitov
2018-08-31 19:07 Stephen Rothwell
2018-09-01 0:06 ` Daniel Borkmann
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=20240814085319.719b42ff@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox