From: Krzysztof Kozlowski <krzk@kernel.org>
To: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Lack of review from Renesas
Date: Wed, 18 Feb 2026 08:58:18 +0100 [thread overview]
Message-ID: <a3f0cb6c-cff7-419f-839b-13bb1ff4960a@kernel.org> (raw)
Hi,
What just happened - sending a patch to fix in-flight (not applied)
patch instead of just reviewing it [1] - is not acceptable. You should
work together, review each other patches and improve them BEFORE they
got merged.
Why? Because you put unnecessary load on maintainers, you allow
knowingly incomplete or buggy or inefficient patches to get in, you do
not collaborate in open source. And I really do not care about your
patch count
If this is how @renesas.com submissions work, I will stop trusting them
and assume your patches are unreviewed internally and buggy.
[1]
https://lore.kernel.org/all/cover.1771344527.git.tommaso.merciai.xr@bp.renesas.com/
Best regards,
Krzysztof
next reply other threads:[~2026-02-18 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 7:58 Krzysztof Kozlowski [this message]
2026-02-18 12:44 ` Lack of review from Renesas Wolfram Sang
2026-03-04 12:31 ` Wolfram Sang
2026-03-04 14:58 ` Krzysztof Kozlowski
2026-03-04 15:13 ` Krzysztof Kozlowski
2026-03-04 17:04 ` Wolfram Sang
2026-03-04 17:00 ` Wolfram Sang
2026-03-05 6:15 ` Wolfram Sang
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=a3f0cb6c-cff7-419f-839b-13bb1ff4960a@kernel.org \
--to=krzk@kernel.org \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.