From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next] bpf: Document BPF licensing.
Date: Wed, 22 Sep 2021 21:20:06 +0000 [thread overview]
Message-ID: <163234560674.6042.16266775340906798652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210917230034.51080-1-alexei.starovoitov@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 17 Sep 2021 16:00:34 -0700 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Document and clarify BPF licensing.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Joe Stringer <joe@cilium.io>
> Acked-by: Lorenz Bauer <lmb@cloudflare.com>
> Acked-by: Dave Thaler <dthaler@microsoft.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
> Acked-by: KP Singh <kpsingh@kernel.org>
>
> [...]
Here is the summary with links:
- [v2,bpf-next] bpf: Document BPF licensing.
https://git.kernel.org/bpf/bpf-next/c/c86216bc96aa
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:[~2021-09-22 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 23:00 [PATCH v2 bpf-next] bpf: Document BPF licensing Alexei Starovoitov
2021-09-22 21:20 ` 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=163234560674.6042.16266775340906798652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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).