public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: bpf@vger.kernel.org, yonghong.song@linux.dev, eddyz87@gmail.com,
	quentin@isovalent.com, ast@kernel.org
Subject: Re: [PATCH -next] bpf: change bpf_alu_sign_string and bpf_movsx_string to static
Date: Fri, 04 Aug 2023 22:40:22 +0000	[thread overview]
Message-ID: <169118882220.4114.11393000838506374611.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230803023128.3753323-1-yangyingliang@huawei.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Thu, 3 Aug 2023 10:31:28 +0800 you wrote:
> The bpf_alu_sign_string and bpf_movsx_string introduced in commit
> f835bb622299 ("bpf: Add kernel/bpftool asm support for new instructions")
> are only used in disasm.c now, change them to static.
> 
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
>  kernel/bpf/disasm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Here is the summary with links:
  - [-next] bpf: change bpf_alu_sign_string and bpf_movsx_string to static
    https://git.kernel.org/bpf/bpf-next/c/09d15054c467

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



      parent reply	other threads:[~2023-08-04 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  2:31 [PATCH -next] bpf: change bpf_alu_sign_string and bpf_movsx_string to static Yang Yingliang
2023-08-03  5:27 ` Yonghong Song
2023-08-04 22: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=169118882220.4114.11393000838506374611.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=quentin@isovalent.com \
    --cc=yangyingliang@huawei.com \
    --cc=yonghong.song@linux.dev \
    /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