From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: Lack of review from Renesas
Date: Thu, 5 Mar 2026 07:15:29 +0100 [thread overview]
Message-ID: <aakfgR3EnLuRULIH@shikoro> (raw)
In-Reply-To: <aahlEKyKF7x2JSuB@shikoro>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
> Okay, if changing status is the only way to get attention: can I then
> get the patchwork permission to change the status when we think they are
> ready?
A maybe simpler idea is to mark the patches as "NeedsAck" instead of
"NotApplicable". This way, they stay in the list but you can still
ignore them until the review counter goes non-zero.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-03-05 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 7:58 Lack of review from Renesas Krzysztof Kozlowski
2026-02-18 12:44 ` 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 [this message]
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=aakfgR3EnLuRULIH@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Chris.Paterson2@renesas.com \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzk@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.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.