From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Ömer PALA" <palaomer100@gmail.com>, "Dan Carpenter" <error27@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: replace msleep with usleep_range
Date: Sat, 19 Sep 2026 09:43:12 +0200 [thread overview]
Message-ID: <8037e424-c642-4928-8381-2261f92bfffe@kernel.org> (raw)
In-Reply-To: <CAKhZXnpwaZf3hF1XAbO6O4fJZFGoe5Lk5Qsck1N_TU-0B170fw@mail.gmail.com>
On 17/09/2026 10:14, Ömer PALA wrote:
> Dan Carpenter <error27@gmail.com> wrote:
>> These kinds of changes need to be tested.
>>
>> I don't love this checkpatch warning because it we reject almost all
>> these patches. If it were new code, presumably the person sending the
>> patch would be able to test it... But I guess it serves as a kind of
>> lesson to not listen to checkpatch and also to search lore before
>> sending stuff.
>> https://lore.kernel.org/all/?q=LPS_Leave_check%20msleep
>>
>> regards,
>> dan carpenter
>
> Sorry for wasting your time.
>
> I thought it was an issue.
>
I kind of told you to look up archives in other thread. Nam Cao told you
this in other thread. Dan told you this in this thread.
Yet, day later on 18th, you decided to send "dt-bindings: iio: adc: Add
dt binding to xlnx,xadc" without checking in archives.
And that one was even pure AI slop.
Mistakes are fine, we all learn from them, but it seems that you are
not. You are just acknowledging the comment and not taking it as anyhow
learning thing, to change something.
I find it not acceptable, because it means we need to repeat you THE
SAME feedback all over again, because you will be always repeating the
same mistake.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-19 7:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 7:19 Omer PALA
2026-09-17 7:50 ` Dan Carpenter
2026-09-17 8:14 ` Ömer PALA
2026-09-19 7:43 ` Krzysztof Kozlowski [this message]
2026-09-17 8:17 ` Nam Cao
2026-09-17 8:24 ` Ömer PALA
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 19:54 [PATCH] staging: rtl8723bs: Replace " AyushMukkanwar
2026-03-19 20:23 ` Ethan Tidmore
2026-03-20 7:42 ` Andy Shevchenko
2026-03-14 5:11 [PATCH] staging: rtl8723bs: replace " Marcos Andrade
2026-03-14 20:56 ` Ethan Tidmore
2026-03-09 0:40 sluisr
2026-03-09 13:33 ` Bryant Boatright
2026-03-09 16:01 ` Greg KH
2026-02-14 17:31 Ofek Almog
2026-02-14 18:11 ` Ethan Tidmore
2026-02-14 18:24 ` Andy Shevchenko
2026-02-14 19:23 ` Ofek Almog
2026-02-15 6:52 ` Greg KH
2026-02-10 5:58 Vo Thanh Cong
2026-02-10 6:37 ` Greg Kroah-Hartman
2026-02-09 12:07 Ethan Lam
2026-02-09 12:35 ` Greg KH
2026-02-08 12:15 Miguel Angel De la Vega Rodriguez
2026-02-08 14:35 ` Greg Kroah-Hartman
2026-01-10 20:44 Işıkhan IŞIK
2026-01-11 12:49 ` Greg KH
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=8037e424-c642-4928-8381-2261f92bfffe@kernel.org \
--to=krzk@kernel.org \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=palaomer100@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®