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,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC] [QUESTION] Stuff to do for string
Date: Thu, 23 Apr 2026 09:11:35 +0200 [thread overview]
Message-ID: <8d1ea0b9-1e94-4d3f-abc4-db9487065ed5@kernel.org> (raw)
In-Reply-To: <8B7C2C02-3E42-4A70-B90F-536D3AA8971B@gmail.com>
On 23/04/2026 08:56, Josh Law wrote:
> On April 23, 2026 7:53:21 AM GMT+01:00, Krzysztof Kozlowski
>>>>>>
>>>>>
>>>>> Krzysztof, haven't you been told to _NOT_ interfere/nack my
>>>>
>>>> You're joking or what?
>>>
>>> Wait, you haven't been told? To not nack my patches if there are
>>> other maintainers??? I'm confused.
>>
>> Stop inventing stories. One more thing you keep lying about. I will be
>> NAKing your patches when you keep sending such arrogant emails "I am
>> representing lib" [1] or you keep pushing untested code to backports [2].
>>
>> [1]
>> https://lore.kernel.org/all/16B7B5A8-EEA7-4580-A565-3A0B4DBB08AB@gmail.com/
>>
>> [2]
>> https://lore.kernel.org/all/C9577A36-B531-4480-BEA5-42F660C184CA@gmail.com/
>>
>> Best regards,
>> Krzysztof
>>
>
> "Unfortunately, I really can't. That's not my jurisdiction. **But I did let
> Krzysztof know that we met. He may still not take your code, but he'll
> refrain from sending out NAKs when you send patches to other
> maintainers.**"
>
>
> Screenshot attached.
>
> That's what I mean. Did you receive a email about that?
Really, this is absolutely unacceptable. Now you bring private
conversation to somehow claim I have no rights to NAK your patches.
You grossly violated that little trust people still were willing to give
you.
Steven asked me about situation, we talked, Steven explained what he did
and what he plans to do, and based on that and his explanation, I SAID
to him that I am willing to give you a chance by refraining to NAK
automatically your patches. And that was before you were doing this:
"I am representing lib"
https://lore.kernel.org/all/16B7B5A8-EEA7-4580-A565-3A0B4DBB08AB@gmail.com/
Pushing untested code to backports
https://lore.kernel.org/all/C9577A36-B531-4480-BEA5-42F660C184CA@gmail.com/
Your claim:
"Wait, you haven't been told? To not nack my patches"
is just arrogance and frankly, what the hell. Using that little trust
you got from Steven in this discussion.
So I do revert my "refrain from NAKs". I will be NAKing your patches,
because after all this time nothing improved.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-23 7:11 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
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 [this message]
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=8d1ea0b9-1e94-4d3f-abc4-db9487065ed5@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 \
--cc=rostedt@goodmis.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®