From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: zijianzhang@bytedance.com, netdev@vger.kernel.org,
linux-api@vger.kernel.org, almasrymina@google.com,
edumazet@google.com, davem@davemloft.net, pabeni@redhat.com,
dsahern@kernel.org, axboe@kernel.dk, shuah@kernel.org,
linux-kselftest@vger.kernel.org, cong.wang@bytedance.com,
xiaochun.lu@bytedance.com
Subject: Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
Date: Wed, 31 Jul 2024 18:29:08 -0700 [thread overview]
Message-ID: <20240731182908.4584a3e1@kernel.org> (raw)
In-Reply-To: <66aab8b37157d_21c08c2941@willemb.c.googlers.com.notmuch>
On Wed, 31 Jul 2024 18:20:35 -0400 Willem de Bruijn wrote:
> Btw patchwork shows red for patch 1/3 due to a new error or warning.
> Not sure if it's a false positive, but take a look.
Patchwork is not for contributors, I keep repeating this :|
Were you not in the room at netdev when I was talking about NIPA
or am I this shit at communicating?
Next person pointing someone to patchwork will get a task to fix
something in NIPA.
next prev parent reply other threads:[~2024-08-01 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 18:41 [PATCH net-next v8 0/3] net: A lightweight zero-copy notification mechanism for MSG_ZEROCOPY zijianzhang
2024-07-30 18:41 ` [PATCH net-next v8 1/3] sock: support copying cmsgs to the user space in sendmsg zijianzhang
2024-07-30 18:41 ` [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control zijianzhang
2024-07-31 22:20 ` Willem de Bruijn
2024-08-01 1:29 ` Jakub Kicinski [this message]
2024-08-01 17:52 ` Willem de Bruijn
2024-07-30 18:41 ` [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test zijianzhang
2024-07-31 22:32 ` Willem de Bruijn
2024-08-01 17:30 ` Zijian Zhang
2024-08-01 17:36 ` Willem de Bruijn
2024-08-01 18:15 ` Zijian Zhang
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=20240731182908.4584a3e1@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=axboe@kernel.dk \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiaochun.lu@bytedance.com \
--cc=zijianzhang@bytedance.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).