All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: patchwork-bot+netdevbpf@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, x86@kernel.org, bpf@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff
Date: Wed, 3 Apr 2024 10:01:01 +0200	[thread overview]
Message-ID: <Zg0Mvb6kkHceEENb@gmail.com> (raw)
In-Reply-To: <CAFULd4Z0RmiWu4Kf0YFBMqA7YFMd65f3J760Do8-h83zWCx9oA@mail.gmail.com>


* Uros Bizjak <ubizjak@gmail.com> wrote:

> > > Here is the summary with links:
> > >   - [RESEND,bpf,v2,1/2] x86/bpf: Fix IP after emitting call depth accounting
> > >     https://git.kernel.org/bpf/bpf/c/9d98aa088386
> > >   - [RESEND,bpf,v2,2/2] x86/bpf: Fix IP for relocating call depth accounting
> > >     https://git.kernel.org/bpf/bpf/c/6a537453000a
> >
> > Just wondering, which kernel version is this targeted for?
> 
> The whole series is intended for the current mainline (v6.9), this is 
> why it is developed against the bpf (*not* bpf-next) branch.

I see - so bpf.git:master are current-mainline BPF fixes - that's perfect.

BTW., bpf-next is not a branch, but a separate Git tree. (Which is what 
confused me.)

Thanks,

	Ingo

  reply	other threads:[~2024-04-03  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 18:55 [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 1/2] x86/bpf: Fix IP after emitting call depth accounting Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 2/2] x86/bpf: Fix IP for relocating " Uros Bizjak
2024-04-02  4:10 ` [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff patchwork-bot+netdevbpf
2024-04-03  7:26   ` Ingo Molnar
2024-04-03  7:43     ` Uros Bizjak
2024-04-03  8:01       ` Ingo Molnar [this message]
2024-04-03  9:04         ` 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=Zg0Mvb6kkHceEENb@gmail.com \
    --to=mingo@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=ubizjak@gmail.com \
    --cc=x86@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.