Re: [External] Re: [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names

2 messages, 2 authors, 2026-03-02 · open the first message on its own page

Re: [External] Re: [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names

From: Jakub Sitnicki <jakub@cloudflare.com>
Date: 2026-03-02 19:25:43

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 :-)

Re: [External] Re: [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names

From: Andrey Grodzovsky <hidden>
Date: 2026-03-02 19:47:39

On Mon, Mar 2, 2026 at 2:25 PM Jakub Sitnicki [off-list ref] wrote:
On Fri, Feb 27, 2026 at 04:15 PM -05, Andrey Grodzovsky wrote:
quoted
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 :-)
Yea, it actually did run for me anyway and your comment explains it.
Anyway, i am dropping the RFC prefix and sending V4 soon.

Andrey
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help