BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Johan Almbladh <johan.almbladh@anyfinetworks.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	paulburton@kernel.org, kafai@fb.com, songliubraving@fb.com,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	tsbogend@alpha.franken.de, bpf@vger.kernel.org,
	linux-mips@vger.kernel.org, netdev@vger.kernel.org,
	lukas.bulwahn@gmail.com
Subject: Re: [PATCH bpf] mips, bpf: Fix reference to non-existing Kconfig symbol
Date: Tue, 30 Nov 2021 16:30:09 +0000	[thread overview]
Message-ID: <163828980909.14069.11489400841762742926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211130160824.3781635-1-johan.almbladh@anyfinetworks.com>

Hello:

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

On Tue, 30 Nov 2021 17:08:24 +0100 you wrote:
> The Kconfig symbol for R10000 ll/sc errata workaround in the MIPS JIT was
> misspelled, causing the workaround to not take effect when enabled.
> 
> Fixes: 72570224bb8f ("mips, bpf: Add JIT workarounds for CPU errata")
> Reported-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Signed-off-by: Johan Almbladh <johan.almbladh@anyfinetworks.com>
> 
> [...]

Here is the summary with links:
  - [bpf] mips, bpf: Fix reference to non-existing Kconfig symbol
    https://git.kernel.org/bpf/bpf/c/099f83aa2d06

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



      reply	other threads:[~2021-11-30 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 16:08 [PATCH bpf] mips, bpf: Fix reference to non-existing Kconfig symbol Johan Almbladh
2021-11-30 16:30 ` 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=163828980909.14069.11489400841762742926.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=johan.almbladh@anyfinetworks.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=tsbogend@alpha.franken.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