From: Song Liu <song@kernel.org>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: Song Liu <songliubraving@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
bpf@vger.kernel.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v5 4/5] powerpc/bpf: rename powerpc64_jit_data to powerpc_jit_data
Date: Thu, 28 Sep 2023 14:09:42 -0700 [thread overview]
Message-ID: <CAPhsuW7TRmqGQ+-sFbUpWV7_8OftKFLpsKjnUzRWvQMyZoTwgQ@mail.gmail.com> (raw)
In-Reply-To: <20230928194818.261163-5-hbathini@linux.ibm.com>
On Thu, Sep 28, 2023 at 12:48 PM Hari Bathini <hbathini@linux.ibm.com> wrote:
>
> powerpc64_jit_data is a misnomer as it is meant for both ppc32 and
> ppc64. Rename it to powerpc_jit_data.
>
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
Acked-by: Song Liu <song@kernel.org>
next prev parent reply other threads:[~2023-09-28 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 19:48 [PATCH v5 0/5] powerpc/bpf: use BPF prog pack allocator Hari Bathini
2023-09-28 19:48 ` [PATCH v5 1/5] powerpc/code-patching: introduce patch_instructions() Hari Bathini
2023-09-28 21:08 ` Song Liu
2023-10-06 18:12 ` Hari Bathini
2023-09-29 8:39 ` Christophe Leroy
2023-10-06 16:22 ` Hari Bathini
2023-10-07 10:35 ` Christophe Leroy
2023-10-10 17:46 ` Christophe Leroy
2023-10-12 20:11 ` Hari Bathini
2023-09-28 19:48 ` [PATCH v5 2/5] powerpc/bpf: implement bpf_arch_text_copy Hari Bathini
2023-09-28 21:08 ` Song Liu
2023-09-28 19:48 ` [PATCH v5 3/5] powerpc/bpf: implement bpf_arch_text_invalidate for bpf_prog_pack Hari Bathini
2023-09-28 21:09 ` Song Liu
2023-09-28 19:48 ` [PATCH v5 4/5] powerpc/bpf: rename powerpc64_jit_data to powerpc_jit_data Hari Bathini
2023-09-28 21:09 ` Song Liu [this message]
2023-09-28 19:48 ` [PATCH v5 5/5] powerpc/bpf: use bpf_jit_binary_pack_[alloc|finalize|free] Hari Bathini
2023-09-28 21:11 ` Song Liu
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=CAPhsuW7TRmqGQ+-sFbUpWV7_8OftKFLpsKjnUzRWvQMyZoTwgQ@mail.gmail.com \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=songliubraving@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;
as well as URLs for NNTP newsgroup(s).