BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-doc@vger.kernel.org, peterz@infradead.org, corbet@lwn.net,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 0/2] Update non-RT users of migrate_disable().
Date: Tue, 30 Nov 2021 14:50:08 +0000	[thread overview]
Message-ID: <163828380868.32639.9644324450074262877.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211127163200.10466-1-bigeasy@linutronix.de>

Hello:

This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat, 27 Nov 2021 17:31:58 +0100 you wrote:
> While browsing through code I noticed outdated code/ documentation
> regarding migrate_disable() on non-PREEMPT_RT kernels.
> 
> Sebastian

Here is the summary with links:
  - [doc,1/2] Documentation/locking/locktypes: Update migrate_disable() bits.
    https://git.kernel.org/bpf/bpf/c/6a631c0432dc
  - [net,2/2] bpf: Make sure bpf_disable_instrumentation() is safe vs preemption.
    https://git.kernel.org/bpf/bpf/c/79364031c5b4

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



      parent reply	other threads:[~2021-11-30 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 16:31 [PATCH 0/2] Update non-RT users of migrate_disable() Sebastian Andrzej Siewior
2021-11-27 16:31 ` [PATCH doc 1/2] Documentation/locking/locktypes: Update migrate_disable() bits Sebastian Andrzej Siewior
2021-11-27 16:32 ` [PATCH net 2/2] bpf: Make sure bpf_disable_instrumentation() is safe vs preemption Sebastian Andrzej Siewior
2021-11-30 14:50 ` 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=163828380868.32639.9644324450074262877.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    --cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox