From: Martin KaFai Lau <martin.lau@linux.dev>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org, kgraul@linux.ibm.com, wenjia@linux.ibm.com,
jaka@linux.ibm.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org
Subject: Re: [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability
Date: Tue, 7 Mar 2023 08:44:10 -0800 [thread overview]
Message-ID: <f1e87004-4654-8204-2771-32ed13467202@linux.dev> (raw)
In-Reply-To: <25cee0eb-a1f9-9f0b-9987-ca6e79e6b752@linux.alibaba.com>
On 3/6/23 7:05 PM, D. Wythe wrote:
> I wondering if there are any more questions about this PATCH, This patch seems
May be start with the questions on v2 first.
> to have been hanging for some time.
>
> If you have any questions, please let me know.
>
>
> Thanks,
>
> D. Wythe
>
>
> Do you have any questions about this PATCH? If you have any other questions,
> please let me know.
>
next prev parent reply other threads:[~2023-03-07 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 16:38 [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 1/4] net/smc: move smc_sock related structure definition D. Wythe
2023-03-08 9:48 ` Tony Lu
2023-02-28 16:38 ` [PATCH bpf-next v4 2/4] bpf: add SMC support in BPF struct_ops D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 3/4] net/smc: add BPF injection on smc negotiation D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 4/4] bpf/selftests: add selftest for SMC bpf capability D. Wythe
2023-02-28 23:02 ` [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability Jakub Kicinski
2023-03-01 2:36 ` D. Wythe
2023-03-07 3:05 ` D. Wythe
2023-03-07 16:44 ` Martin KaFai Lau [this message]
2023-03-08 5:58 ` D. Wythe
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=f1e87004-4654-8204-2771-32ed13467202@linux.dev \
--to=martin.lau@linux.dev \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wenjia@linux.ibm.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.