All of lore.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 10:12:32 -0700	[thread overview]
Message-ID: <0d21d5ae-fa4d-49f2-a9ff-a8a0600d0dc0@kernel.dk> (raw)
In-Reply-To: <71202db3-1aac-4b0b-9b52-1f3d074ac41b@gmail.com>

On 2/26/26 10:10 AM, Pavel Begunkov wrote:
> On 2/26/26 17:06, Jens Axboe wrote:
>> On 2/26/26 10:03 AM, Pavel Begunkov wrote:
>>> On 2/26/26 15:16, Jens Axboe wrote:
>>>> 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.
>>>
>>> Well, whatever it's called, I might just use it if it saves time
>>> for writing man pages. Does it require any attribution / tags in the
>>> commit? Some Assisted-by?
>>
>> I'll save you a lot of time...
> 
> "_I_ will", looks like AI already replaced Jens...

Oops, missing a t - It'll :)

>> I don't care if you put the tag in there or not. For the kernel, and for
>> actual code, I do believe an assisted-by tag is required. But for
>> documentation or liburing, as far as I'm concerned, you can add
>> attribution or not, doesn't matter to me.
> 
> Got it, and I wasn't planning to use it for the kernel

It's most useful for documentation and tests on the liburing side. It
does a pretty decent job on the latter too, mimicking things like "skip
on old kernels" and that kind of thing. Needs a bit of nudging on little
things, but once dialed in, that part is a big time saver too.

-- 
Jens Axboe

  reply	other threads:[~2026-02-26 17:12 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
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 [this message]
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=0d21d5ae-fa4d-49f2-a9ff-a8a0600d0dc0@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 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.