public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org, bpf@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Björn Töpel" <bjorn@kernel.org>, "Yonghong Song" <yhs@fb.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Martin KaFai Lau" <martin.lau@linux.dev>,
	"Song Liu" <song@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"KP Singh" <kpsingh@kernel.org>,
	"Stanislav Fomichev" <sdf@google.com>,
	"Hao Luo" <haoluo@google.com>, "Jiri Olsa" <jolsa@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Xu Kuohai" <xukuohai@huawei.com>,
	"Puranjay Mohan" <puranjay12@gmail.com>,
	"Pu Lehui" <pulehui@huawei.com>
Subject: Re: [PATCH bpf-next v2 0/7] Add support cpu v4 insns for RV64
Date: Wed, 23 Aug 2023 18:53:56 -0700	[thread overview]
Message-ID: <20230823185356.0db6cc1d@kernel.org> (raw)
In-Reply-To: <20230824095001.3408573-1-pulehui@huaweicloud.com>

On Thu, 24 Aug 2023 09:49:54 +0000 Pu Lehui wrote:
> Add support cpu v4 instructions for RV64.

Please make sure you fix the timezone on your system before sending 
out the next version.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-08-24  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  9:49 [PATCH bpf-next v2 0/7] Add support cpu v4 insns for RV64 Pu Lehui
2023-08-24  1:53 ` Jakub Kicinski [this message]
2023-08-24  2:05   ` Pu Lehui
2023-08-24  8:46 ` Björn Töpel
2023-08-24  9:49 ` [PATCH bpf-next v2 1/7] riscv, bpf: Fix missing exception handling and redundant zext for LDX_B/H/W Pu Lehui
2023-08-24  9:49 ` [PATCH bpf-next v2 2/7] riscv, bpf: Support sign-extension load insns Pu Lehui
2023-08-24  9:49 ` [PATCH bpf-next v2 3/7] riscv, bpf: Support sign-extension mov insns Pu Lehui
2023-08-24  8:44   ` Björn Töpel
2023-08-24  9:49 ` [PATCH bpf-next v2 4/7] riscv, bpf: Support 32-bit offset jmp insn Pu Lehui
2023-08-24  9:49 ` [PATCH bpf-next v2 5/7] riscv, bpf: Support signed div/mod insns Pu Lehui
2023-08-24  9:50 ` [PATCH bpf-next v2 6/7] riscv, bpf: Support unconditional bswap insn Pu Lehui
2023-08-24  9:50 ` [PATCH bpf-next v2 7/7] selftests/bpf: Enable cpu v4 tests for RV64 Pu Lehui
2023-08-24 16:20 ` [PATCH bpf-next v2 0/7] Add support cpu v4 insns " 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=20230823185356.0db6cc1d@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.com \
    --cc=puranjay12@gmail.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=xukuohai@huawei.com \
    --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