From: Yonghong Song <yonghong.song@linux.dev>
To: Yang Yingliang <yangyingliang@huawei.com>, bpf@vger.kernel.org
Cc: 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: Wed, 2 Aug 2023 22:27:03 -0700 [thread overview]
Message-ID: <efaae4e7-7c90-9c34-5232-de406fad23d5@linux.dev> (raw)
In-Reply-To: <20230803023128.3753323-1-yangyingliang@huawei.com>
On 8/2/23 7:31 PM, Yang Yingliang 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>
Thanks for the fix!
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2023-08-03 5:27 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 [this message]
2023-08-04 22:40 ` patchwork-bot+netdevbpf
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=efaae4e7-7c90-9c34-5232-de406fad23d5@linux.dev \
--to=yonghong.song@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=quentin@isovalent.com \
--cc=yangyingliang@huawei.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