From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf-next 2023-05-26
Date: Fri, 26 May 2023 17:30:03 -0700 [thread overview]
Message-ID: <20230526173003.55cad641@kernel.org> (raw)
In-Reply-To: <20230526222747.17775-1-daniel@iogearbox.net>
On Sat, 27 May 2023 00:27:47 +0200 Daniel Borkmann wrote:
> 1) Add the capability to destroy sockets in BPF through a new kfunc, from Aditi Ghag.
Is there a reason this wasn't CCed to netdev?
next prev parent reply other threads:[~2023-05-27 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 22:27 pull-request: bpf-next 2023-05-26 Daniel Borkmann
2023-05-27 0:30 ` Jakub Kicinski [this message]
2023-05-30 9:29 ` Daniel Borkmann
2023-05-30 19:20 ` Jakub Kicinski
2023-05-27 1:06 ` 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=20230526173003.55cad641@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).