From: Krzysztof Kozlowski <krzk@kernel.org>
To: Josh Law <joshlaw48@gmail.com>,
akpm@linux-foundation.org, andriy.shevchenko@intel.com,
kees@kernel.org, James.Bottomley@hansenpartnership.com,
linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com
Subject: Re: [RFC] [QUESTION] Stuff to do for string
Date: Thu, 23 Apr 2026 08:24:50 +0200 [thread overview]
Message-ID: <deff4afd-425c-490f-928d-2f42dc90de2d@kernel.org> (raw)
In-Reply-To: <CBE4ACA4-F052-4D9C-8816-139A990AF7CB@gmail.com>
On 22/04/2026 16:57, Josh Law wrote:
> Hello, (this is my first RFC, so maybe cc is bad, but yeah)
>
> What do you guys have planned/would like me to have a look at doing in
> lib/string.c
Do nothing. As some people already said: go away.
You were lying multiple times, including how you tested the patches and
that you claim you have device being worked on:
"I own this device"
https://lore.kernel.org/all/f8772114-a495-409b-a590-a9b1d8ed1d41@gmail.com/
Even after proving you fabricated absolute AI slop you claimed otherwise:
"The commit descriptions (The long ones), Use AI, to be exact! "
https://lore.kernel.org/all/043CED5F-7014-4776-824E-07E027B7BDC3@objecting.org/
https://lore.kernel.org/all/04B79050-4353-4FD2-A596-1474BDB94B3F@objecting.org/
So no, we do not want you to look at anything. You were told that
multiple times.
Just because one maintainer gives you chance, it still means - don't
touch /lib or any other part of core kernel.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-23 6:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 14:57 Josh Law
2026-04-22 16:12 ` Andy Shevchenko
2026-04-22 16:28 ` Josh Law
2026-04-22 16:51 ` Andy Shevchenko
2026-04-22 16:56 ` Josh Law
2026-04-22 19:23 ` Andy Shevchenko
2026-04-22 19:25 ` Josh Law
2026-04-22 23:13 ` Kees Cook
2026-04-22 23:27 ` Josh Law
2026-04-23 6:24 ` Krzysztof Kozlowski [this message]
2026-04-23 6:29 ` Josh Law
2026-04-23 6:44 ` Krzysztof Kozlowski
2026-04-23 6:46 ` Josh Law
2026-04-23 6:53 ` Krzysztof Kozlowski
2026-04-23 6:56 ` Josh Law
2026-04-23 7:11 ` Krzysztof Kozlowski
2026-04-23 7:37 ` Andy Shevchenko
2026-04-23 12:32 ` Steven Rostedt
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=deff4afd-425c-490f-928d-2f42dc90de2d@kernel.org \
--to=krzk@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=joshlaw48@gmail.com \
--cc=kees@kernel.org \
--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®