From: Jakub Sitnicki <jakub@cloudflare.com>
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf <bpf@vger.kernel.org>,
DL Linux Open Source Team <linux-open-source@crowdstrike.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel <linux-trace-kernel@vger.kernel.org>
Subject: Re: [External] Re: [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names
Date: Mon, 02 Mar 2026 20:25:39 +0100 [thread overview]
Message-ID: <87fr6idoek.fsf@cloudflare.com> (raw)
In-Reply-To: <CAOu3gNhBcW-JQ_VQ00GnLd8iB6xu7Ew80Bs4VHoXOct5g-wr4g@mail.gmail.com> (Andrey Grodzovsky's message of "Fri, 27 Feb 2026 16:15:07 -0500")
On Fri, Feb 27, 2026 at 04:15 PM -05, Andrey Grodzovsky wrote:
> Hey Alexei, just to be clear, do you mean drop the entire RFC letter or,
> Drop the RFC prefix from the letter so the CI pipeline can be properly
> triggered ?
The prefix, not the cover letter.
Although I think swapping the word order might also work ("PATCH RFC").
I've seen CI run for my patch set when it was titled like that.
Kind reminder to not top-post :-)
next prev parent reply other threads:[~2026-03-02 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 20:40 [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 1/3] libbpf: " Andrey Grodzovsky
2026-02-27 21:17 ` bot+bpf-ci
2026-02-27 22:28 ` [External] " Andrey Grodzovsky
2026-03-02 10:58 ` Jiri Olsa
2026-03-02 17:37 ` Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 2/3] ftrace: Use kallsyms binary search for single-symbol lookup Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 3/3] selftests/bpf: add tests for kprobe.session optimization Andrey Grodzovsky
2026-02-27 20:43 ` [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names Alexei Starovoitov
2026-02-27 21:15 ` [External] " Andrey Grodzovsky
2026-03-02 19:25 ` Jakub Sitnicki [this message]
2026-03-02 19:47 ` Andrey Grodzovsky
2026-03-02 12:47 ` Jakub Sitnicki
2026-03-02 18:00 ` [External] " Andrey Grodzovsky
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=87fr6idoek.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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