mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@nvidia.com>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	shashank <jain.sm@gmail.com>, Yury Norov <yury.norov@gmail.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-kernel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/6] bitmap: fix three parsing bugs in bitmap_parse() and bitmap_parselist()
Date: Wed, 30 Sep 2026 20:23:46 -0400	[thread overview]
Message-ID: <ar2oEnD8i3qP2Dkq@yury> (raw)
In-Reply-To: <1237394198.791420.1790808408141@kpc.webmail.kpnmail.nl>

On Thu, Oct 01, 2026 at 12:46:48AM +0200, Jori Koolstra wrote:
> 
> > Op 26-09-2026 10:02 EDT schreef Yury Norov <ynorov@nvidia.com>:
> > 
> >  
> > + people from 816d9992d9ed
> > 
> > On Fri, Sep 25, 2026 at 01:39:51PM -0700, Andrew Morton wrote:
> > > On Fri, 25 Sep 2026 13:05:06 -0400 Yury Norov <ynorov@nvidia.com> wrote:
> > 
> > ...
> > 
> > > > That looks reasonable, but please resend the series with your full
> > > > real name, and also specify the version of LLM you've used to prepare
> > > > the series. I'm uncomfortable taking anonymous commitments.
> > > 
> > > fyi, this was changed by 816d9992d9ed ("coding-assistants: simplify
> > > attribution") - see latest Documentation/process/coding-assistants.rst.
> > > 
> > > So now everything is supposed to say only "Assisted-by: LLM".  I find
> > > this regrettable - I'm interested in seeing what people are using.  Oh
> > > well.
> > 
> > Huh... The commit says: "provides free advertising to proprietary
> > software companies", and that makes no sense to me. My email does
> > exactly the same thing, together with the emails of the  vast
> > majority of the community.
> > 
> > Can we please somehow revert this "simplification"? If people use
> > some wonder tool, and it helps - I want to know the latest best
> > practices. I want to know MORE rather than LESS.
> > 
> 
> The analogy has no bite. No one is making huge bucks off marketing specific
> email providers to kernel devs.

Alright... My 'email provider' is NVIDIA. It makes huge bucks in many
different ways. Particularly by hiring excellent kernel engineers,
and advertising itself directly in the kernel mailing list to hire
more.

> Also, we can't get rid of mentioning
> email addresses. You need that information. You don't need to know model
> specifics, and it has nothing to do with best practices.

Please stop speculating about what I need. I put it clear: I need
to know which models my contributors use to prepare patches. 

> I think you'll be able to find out about wonderful new LLM models also
> without the tagline. They are after all shoved down our throats at every
> opportunity.

Again, please stop speculating about what I'm able to do and what not.
I show you what I'm definitely able to do:

  $ git log | grep Assisted-by | sort | uniq -c | sort -hr | head
    209     Assisted-by: Claude:claude-opus-4-8
    169     Assisted-by: Claude:claude-opus-4.6
    161     Assisted-by: LLM
    140     Assisted-by: Claude:claude-opus-4-6
    112     Assisted-by: Antigravity:gemini-3.5-flash
     93     Assisted-by: Claude:claude-opus-5
     93     Assisted-by: Claude:claude-opus-4-7
     84     Assisted-by: Claude:claude-sonnet-4-6
     79     Assisted-by: Copilot:Claude-Opus-4.8
     72     Assisted-by: Gemini:gemini-3.1-pro

See that? Your wonderful innovation already made this 'LLM' crap #3 in
the list. Now please explain how should I motivate myself to try a new
rising star model named 'LLM', and how should I convince my manager to
pay for it?
 
> This will I presume be discussed at the maintainer summit, but there
> was quite a bit of consensus (iirc) to bring something akin to the current
> systemd AI policy to that kernel document. So, emphasizing what the LLM was
> put to do, keeping only the short assisted-by tag for quick filtering and as
> an alibi to point people towards this document.

You guys discuss whatever you want and celebrate each other with the
consensus you've reached. Just let me and other sane people to share
important information through the tags, as we normally do.

Thanks,
Yury

      reply	other threads:[~2026-10-01  0:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:23 shashank
2026-09-25 10:23 ` [PATCH 1/6] bitmap: bitmap_parse(): reject non-hex character before 8 digits shashank
2026-09-25 10:23 ` [PATCH 2/6] bitmap: test bitmap_parse() with an illegal character before 8 hex digits shashank
2026-09-25 10:23 ` [PATCH 3/6] bitmap: bitmap_parselist(): reject trailing characters after group size shashank
2026-09-25 10:23 ` [PATCH 4/6] bitmap: test bitmap_parselist() with text after the " shashank
2026-09-25 10:23 ` [PATCH 5/6] bitmap: bitmap_parselist(): don't wrap around on a huge " shashank
2026-09-25 10:23 ` [PATCH 6/6] bitmap: test bitmap_parselist() with a group size close to UINT_MAX shashank
2026-09-25 17:05 ` [PATCH 0/6] bitmap: fix three parsing bugs in bitmap_parse() and bitmap_parselist() Yury Norov
2026-09-25 20:39   ` Andrew Morton
2026-09-26 14:02     ` Yury Norov
2026-09-30 22:46       ` Jori Koolstra
2026-10-01  0:23         ` Yury Norov [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=ar2oEnD8i3qP2Dkq@yury \
    --to=ynorov@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=jain.sm@gmail.com \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=ljs@kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=yury.norov@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®