From: patchwork-bot+netdevbpf@kernel.org
To: Brendan Jackman <jackmanb@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii.nakryiko@gmail.com, kpsingh@chromium.org,
revest@chromium.org, linux-kernel@vger.kernel.org,
bjorn.topel@gmail.com, john.fastabend@gmail.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v7 00/11] Atomics for eBPF
Date: Fri, 15 Jan 2021 03:20:11 +0000 [thread overview]
Message-ID: <161068081127.31171.9881171165657738876.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114181751.768687-1-jackmanb@google.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 14 Jan 2021 18:17:40 +0000 you wrote:
> There's still one unresolved review comment from John[3] which I
> will resolve with a followup patch.
>
> Differences from v6->v7 [1]:
>
> * Fixed riscv build error detected by 0-day robot.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,01/11] bpf: x86: Factor out emission of ModR/M for *(reg + off)
https://git.kernel.org/bpf/bpf-next/c/11c11d0751fc
- [bpf-next,v7,02/11] bpf: x86: Factor out emission of REX byte
https://git.kernel.org/bpf/bpf-next/c/74007cfc1f71
- [bpf-next,v7,03/11] bpf: x86: Factor out a lookup table for some ALU opcodes
https://git.kernel.org/bpf/bpf-next/c/e5f02caccfae
- [bpf-next,v7,04/11] bpf: Rename BPF_XADD and prepare to encode other atomics in .imm
https://git.kernel.org/bpf/bpf-next/c/91c960b00566
- [bpf-next,v7,05/11] bpf: Move BPF_STX reserved field check into BPF_STX verifier code
https://git.kernel.org/bpf/bpf-next/c/c5bcb5eb4db6
- [bpf-next,v7,06/11] bpf: Add BPF_FETCH field / create atomic_fetch_add instruction
https://git.kernel.org/bpf/bpf-next/c/5ca419f2864a
- [bpf-next,v7,07/11] bpf: Add instructions for atomic_[cmp]xchg
https://git.kernel.org/bpf/bpf-next/c/5ffa25502b5a
- [bpf-next,v7,08/11] bpf: Pull out a macro for interpreting atomic ALU operations
https://git.kernel.org/bpf/bpf-next/c/462910670e4a
- [bpf-next,v7,09/11] bpf: Add bitwise atomic instructions
https://git.kernel.org/bpf/bpf-next/c/981f94c3e921
- [bpf-next,v7,10/11] bpf: Add tests for new BPF atomic operations
https://git.kernel.org/bpf/bpf-next/c/98d666d05a1d
- [bpf-next,v7,11/11] bpf: Document new atomic instructions
https://git.kernel.org/bpf/bpf-next/c/de948576f8e7
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:[~2021-01-15 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 18:17 [PATCH bpf-next v7 00/11] Atomics for eBPF Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 01/11] bpf: x86: Factor out emission of ModR/M for *(reg + off) Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 02/11] bpf: x86: Factor out emission of REX byte Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 03/11] bpf: x86: Factor out a lookup table for some ALU opcodes Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 04/11] bpf: Rename BPF_XADD and prepare to encode other atomics in .imm Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 05/11] bpf: Move BPF_STX reserved field check into BPF_STX verifier code Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 06/11] bpf: Add BPF_FETCH field / create atomic_fetch_add instruction Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 07/11] bpf: Add instructions for atomic_[cmp]xchg Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 08/11] bpf: Pull out a macro for interpreting atomic ALU operations Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 09/11] bpf: Add bitwise atomic instructions Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 10/11] bpf: Add tests for new BPF atomic operations Brendan Jackman
2021-01-14 18:17 ` [PATCH bpf-next v7 11/11] bpf: Document new atomic instructions Brendan Jackman
2021-01-15 3:20 ` patchwork-bot+netdevbpf [this message]
2021-01-15 3:23 ` [PATCH bpf-next v7 00/11] Atomics for eBPF Alexei Starovoitov
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=161068081127.31171.9881171165657738876.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=revest@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.