From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm4udG9wZWxAZ21haWwuY29tPg==?=@ci.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, xi.wang@gmail.com, luke.r.nels@gmail.com,
linux-riscv@lists.infradead.org, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v2 0/3] RISC-V selftest/bpf fixes
Date: Thu, 19 Nov 2020 02:00:05 +0000 [thread overview]
Message-ID: <160575120591.17801.17784029868149830449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201118071640.83773-1-bjorn.topel@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 18 Nov 2020 08:16:37 +0100 you wrote:
> This series contain some fixes for selftests/bpf when building/running
> on a RISC-V host. Details can be found in each individual commit.
>
>
> Cheers,
> Björn
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] selftests/bpf: Fix broken riscv build
https://git.kernel.org/bpf/bpf-next/c/6016df8fe874
- [bpf-next,v2,2/3] selftests/bpf: Avoid running unprivileged tests with alignment requirements
https://git.kernel.org/bpf/bpf-next/c/c77b0589ca29
- [bpf-next,v2,3/3] selftests/bpf: Mark tests that require unaligned memory access
https://git.kernel.org/bpf/bpf-next/c/6007b23cc755
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-11-19 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 7:16 [PATCH bpf-next v2 0/3] RISC-V selftest/bpf fixes Björn Töpel
2020-11-18 7:16 ` [PATCH bpf-next v2 1/3] selftests/bpf: Fix broken riscv build Björn Töpel
2020-11-18 7:16 ` [PATCH bpf-next v2 2/3] selftests/bpf: Avoid running unprivileged tests with alignment requirements Björn Töpel
2020-11-18 7:16 ` [PATCH bpf-next v2 3/3] selftests/bpf: Mark tests that require unaligned memory access Björn Töpel
2020-11-18 17:43 ` [PATCH bpf-next v2 0/3] RISC-V selftest/bpf fixes Luke Nelson
2020-11-19 2:00 ` patchwork-bot+netdevbpf [this message]
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=160575120591.17801.17784029868149830449.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm4udG9wZWxAZ21haWwuY29tPg==?=@ci.codeaurora.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xi.wang@gmail.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).