public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing v2 1/1] tests: test timeout with immediate arguments
Date: Thu, 26 Feb 2026 08:16:47 -0700	[thread overview]
Message-ID: <8b987673-33d8-4f0f-a13a-1c1f963f9afe@kernel.dk> (raw)
In-Reply-To: <d718db45-cd6c-4d89-ac9c-8f073d31eaa7@gmail.com>

On 2/26/26 5:52 AM, Pavel Begunkov wrote:
>> Applied, but there's no documentation update included. I'm just going to
>> auto-generate one so we have it, we should not add new flags without
>> documenting them in the appropriate man page(s). Same old story...
> 
> Looks like you've been generating AI slop for docs, so I assume
> you're not against it? I'll try generating it next time.

I think calling it "slop" is a bit unfair - sometimes it does get
nuances slightly wrong, but it's a LOT easier to fix those up than write
it from scratch yourself. And the the language is a lot better than what
you or I can produce. The icing on the cake is that I no longer have to
nag you or others on documentation - though I would prefer if you or
whoever is the submitted generated it and proof read it, I think that's
the better approach than me doing it.

-- 
Jens Axboe

  reply	other threads:[~2026-02-26 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 17:28 [PATCH liburing v2 1/1] tests: test timeout with immediate arguments Pavel Begunkov
2026-02-25 18:07 ` Jens Axboe
2026-02-26 12:52   ` Pavel Begunkov
2026-02-26 15:16     ` Jens Axboe [this message]
2026-02-26 17:03       ` Pavel Begunkov
2026-02-26 17:06         ` Jens Axboe
2026-02-26 17:10           ` Pavel Begunkov
2026-02-26 17:12             ` Jens Axboe
2026-02-25 18:25 ` 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=8b987673-33d8-4f0f-a13a-1c1f963f9afe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@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