From: patchwork-bot+linux-riscv@kernel.org
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, pulehui@huawei.com,
conor.dooley@microchip.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, kpsingh@kernel.org, bjorn@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/4] bpf, riscv: use BPF prog pack allocator in BPF JIT
Date: Wed, 06 Sep 2023 02:50:27 +0000 [thread overview]
Message-ID: <169396862749.1987.4994366714692856707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230831131229.497941-1-puranjay12@gmail.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 31 Aug 2023 13:12:25 +0000 you wrote:
> Changes in v3 -> v4:
> 1. Add Acked-by:, Tested-by:, etc.
> 2. Add the core BPF patch[3] which was earlier sent with ARM64 series to
> this series so it can go with this.
>
> Changes in v2 -> v3:
> 1. Fix maximum width of code in patches from 80 to 100. [All patches]
> 2. Add checks for ctx->ro_insns == NULL. [Patch 3]
> 3. Fix check for edge condition where amount of text to set > 2 * pagesize
> [Patch 1 and 2]
> 4. Add reviewed-by in patches.
> 5. Adding results of selftest here:
> Using the command: ./test_progs on qemu
> Without the series: Summary: 336/3162 PASSED, 56 SKIPPED, 90 FAILED
> With this series: Summary: 336/3162 PASSED, 56 SKIPPED, 90 FAILED
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/4] bpf: make bpf_prog_pack allocator portable
https://git.kernel.org/riscv/c/063119d90a06
- [bpf-next,v4,2/4] riscv: extend patch_text_nosync() for multiple pages
https://git.kernel.org/riscv/c/fb81d562ed1f
- [bpf-next,v4,3/4] riscv: implement a memset like function for text
https://git.kernel.org/riscv/c/f071fe652d73
- [bpf-next,v4,4/4] bpf, riscv: use prog pack allocator in the BPF JIT
https://git.kernel.org/riscv/c/19ea9d201008
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-09-06 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 13:12 [PATCH bpf-next v4 0/4] bpf, riscv: use BPF prog pack allocator in BPF JIT Puranjay Mohan
2023-08-31 13:12 ` [PATCH bpf-next v4 1/4] bpf: make bpf_prog_pack allocator portable Puranjay Mohan
2023-08-31 13:12 ` [PATCH bpf-next v4 2/4] riscv: extend patch_text_nosync() for multiple pages Puranjay Mohan
2023-08-31 13:12 ` [PATCH bpf-next v4 3/4] riscv: implement a memset like function for text Puranjay Mohan
2023-08-31 13:12 ` [PATCH bpf-next v4 4/4] bpf, riscv: use prog pack allocator in the BPF JIT Puranjay Mohan
2023-08-31 21:19 ` [PATCH bpf-next v4 0/4] bpf, riscv: use BPF prog pack allocator in " Daniel Borkmann
2023-09-06 2:50 ` patchwork-bot+linux-riscv [this message]
2023-09-06 13:31 ` Palmer Dabbelt
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=169396862749.1987.4994366714692856707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pulehui@huawei.com \
--cc=puranjay12@gmail.com \
--cc=song@kernel.org \
--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