From: lollipopkit <a@lolli.tech>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Pavel Begunkov <asml.silence@gmail.com>,
Willem de Bruijn <willemb@google.com>,
Richard Cochran <richardcochran@gmail.com>,
io-uring@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] io_uring/cmd_net: drop unextractable TX_TIMESTAMP skbs instead of requeueing
Date: Tue, 29 Sep 2026 23:35:28 +0800 [thread overview]
Message-ID: <20260929153426.90278d054c98-a@lolli.tech> (raw)
In-Reply-To: <willemdebruijn.kernel.570e0a646f4@gmail.com>
On Tue, 29 Sep 2026 11:06:26 -0400, Willem de Bruijn wrote:
> lollipopkit wrote:
>> Assisted-by: Claude:claude-opus-5-5
>> Signed-off-by: lollipopkit <a@lolli.tech>
>
> Is this a real name?
>
> https://docs.kernel.org/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
>
> "a known identity (sorry, no anonymous contributions.)"
It is not my legal name. It is the handle I have used publicly for
years, including on GitHub (https://github.com/lollipopkit), and it is
the identity I sign all my kernel work with. My understanding is that
this is what d4563201f33a ("Documentation: simplify and clarify DCO
contribution example language") intended by "known identity".
The earlier CQ-full fix (3a3d93070c5e) went in under the same name.
If that is not sufficient for this tree, let me know what you need.
prev parent reply other threads:[~2026-09-29 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 4:54 lollipopkit
2026-09-29 15:06 ` Willem de Bruijn
2026-09-29 15:35 ` lollipopkit [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=20260929153426.90278d054c98-a@lolli.tech \
--to=a@lolli.tech \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@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
all inboxes | Powered by JetHome®