From: Jens Axboe <axboe@kernel.dk>
To: Jann Horn <jannh@google.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/register: fix comment about task_no_new_privs
Date: Mon, 9 Mar 2026 08:40:09 -0600 [thread overview]
Message-ID: <3adb3dee-9707-499c-88ad-43b887f99586@kernel.dk> (raw)
In-Reply-To: <20260309-uring-nnp-comment-fix-v1-1-e7d185527142@google.com>
On 3/9/26 8:34 AM, Jann Horn wrote:
> The actual code is right, but the comment is the wrong way around.
Huh indeed, wonder how that happened. Thanks for spotting that, will get
it added.
--
Jens Axboe
next prev parent reply other threads:[~2026-03-09 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:34 [PATCH] io_uring/register: fix comment about task_no_new_privs Jann Horn
2026-03-09 14:40 ` Jens Axboe [this message]
2026-03-09 14:52 ` Jens Axboe
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=3adb3dee-9707-499c-88ad-43b887f99586@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@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