All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com,
	agordeev@linux.ibm.com
Subject: Re: [PATCH 0/2] bpf/s390: Implement get_preempt_count()
Date: Tue, 03 Mar 2026 16:40:23 +0000	[thread overview]
Message-ID: <177255602330.1378092.784944008193338204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260217160813.100855-1-iii@linux.ibm.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 17 Feb 2026 17:05:07 +0100 you wrote:
> Hi,
> 
> This series adds get_preempt_count() BPF implementation for s390.
> On s390 preempt_count lives in lowcore: a per-cpu data structure
> mapped at virtual address 0 or 0x70000 depending on the kernel
> command line.
> 
> [...]

Here is the summary with links:
  - [1/2] s390: Introduce bpf_get_lowcore() kfunc
    https://git.kernel.org/bpf/bpf-next/c/6fe54677bcc2
  - [2/2] bpf/s390: Implement get_preempt_count()
    https://git.kernel.org/bpf/bpf-next/c/0f87614c4dbd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-03 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 16:05 [PATCH 0/2] bpf/s390: Implement get_preempt_count() Ilya Leoshkevich
2026-02-17 16:05 ` [PATCH 1/2] s390: Introduce bpf_get_lowcore() kfunc Ilya Leoshkevich
2026-02-17 16:05 ` [PATCH 2/2] bpf/s390: Implement get_preempt_count() Ilya Leoshkevich
2026-02-17 17:55 ` [PATCH 0/2] " Vasily Gorbik
2026-02-17 19:32   ` Alexei Starovoitov
2026-02-17 23:34     ` Ilya Leoshkevich
2026-02-18  0:18       ` Alexei Starovoitov
2026-03-03 16:40 ` patchwork-bot+netdevbpf [this message]

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=177255602330.1378092.784944008193338204.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    /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.