mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Taraba <peter.schuster.taraba@gmail.com>
To: corbet@lwn.net
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	peter.schuster.taraba@gmail.com
Subject: Re: [PATCH] lib: add statsort(), a distribution/bucket sort
Date: Wed,  5 Aug 2026 08:47:15 -0700	[thread overview]
Message-ID: <20260805154715.5415-1-peter.schuster.taraba@gmail.com> (raw)
In-Reply-To: <875x1or67m.fsf@trenco.lwn.net>

Hi Jon and anyone who is reading it,

here are your answers:

>> We don't add new code to the kernel for users that are "secrets".  If
>> you have an intended user for this code, include it with the series,
>> please.

I guess I will just go ahead and do it through my work around and keep my
secrets (dont need to get my ideas to Microsoft, Google or even worse -
to Facebook, etc. for free). If you change your mind about it in future,
please do let me know.

>> There is a recursive function in there, which we tend to avoid for the
>> kernel.  At a minimum, you would need to provide a convincing
>> explanation of how you prevent it from overrunning the kernel stack.

I am fully aware. Wanted more feedback (not only feedback which I get from AI).
Thank you.

>> Until you showed up with this patch, you have never been seen on the
>> kernel lists; what inspired you to make this change now?  Was this code
>> created with assistance from large language models?

I wanted to contribute to linux kernel as I am linux user and it would
be nice to contribute to Linux community (kind of a proud moment for me).
Oh well.

Also, you should do code review, not ask useless questions if LLM wrote the
code. Even if I answered your questions, you wouldn't have to believe me -
so what's the point of asking. You should make decision based on the code
and if it is good for Linux kernel purely.

Cheers,
Peter

  reply	other threads:[~2026-08-05 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMKTnsb-PZ7_4Zd1ZAtmSWnTk8vyoP07WZUDsLuZ21j7OawQ9g@mail.gmail.com>
2026-08-05  0:35 ` Andrew Morton
2026-08-05  0:47   ` Peter Taraba
2026-08-05 14:29     ` Jonathan Corbet
2026-08-05 15:47       ` Peter Taraba [this message]
2026-08-05 16:39         ` Jonathan Corbet
2026-08-05 18:44           ` Peter Taraba
2026-08-10 10:22             ` Kuan-Wei Chiu
2026-08-10 13:24               ` Peter Taraba
2026-08-10 15:09                 ` Bradley Morgan
2026-08-10 15:59                   ` Peter Taraba
2026-08-10 16:07                     ` Bradley Morgan
2026-08-04 23:34 Peter Taraba
2026-08-04 23:58 ` Andrew Morton

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=20260805154715.5415-1-peter.schuster.taraba@gmail.com \
    --to=peter.schuster.taraba@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --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

all inboxes | Powered by JetHome®