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: Wed, 4 Mar 2026 18:00:00 +0100 [thread overview]
Message-ID: <aahlEKyKF7x2JSuB@shikoro> (raw)
In-Reply-To: <8efddf8f-a9d3-4c29-b54f-201304339843@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
Hi Krzysztof,
> No problem, I will be marking patches as N/A in patchwork. Just have in
> mind that they will not re-appear on the queue and pinging won't work,
> because it does not change status of Patchwork.
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?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-04 17:00 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 [this message]
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=aahlEKyKF7x2JSuB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox