From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jassi Brar <jassisinghbrar@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation
Date: Tue, 31 Mar 2026 09:18:01 +0200 [thread overview]
Message-ID: <28396df7-bb9f-4a6a-963c-0b56c66fb3cd@kernel.org> (raw)
In-Reply-To: <actzUSIKKzcDmBCT@shikoro>
On 31/03/2026 09:10, Wolfram Sang wrote:
>
>> I did not get the driver so I cannot verify that. What sort of Linux ABI
>> does this bind?
>
> In case you mean this as unanswered questions to v1: This describes the
> device specific second mbox cell. Like Tegra does it here (even with
> shifts instead of plain numbers):
>
> include/dt-bindings/mailbox/tegra186-hsp.h
>
> But all this has been said before and you got the driver as well in v2.
> I really have no idea what is still missing?
And look when my question was asked:
19th of Match:
"I did not get the driver so I cannot verify that. What sort of Linux
ABI does this bind?"
You ignore it and on 23rd of Match you send v2.
And now you reply that "you got driver as well in v2". Seriously? How
can I move from 19th Match into the future of 23rd to get the email from
the future? And some answers from the future?
Respond to review instead of ignoring it and sending v2.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-31 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 13:06 [PATCH 0/3] soc: renesas: add MFIS driver Wolfram Sang
2026-03-17 13:06 ` [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation Wolfram Sang
2026-03-18 9:17 ` Krzysztof Kozlowski
2026-03-18 9:19 ` Krzysztof Kozlowski
2026-03-19 8:54 ` Geert Uytterhoeven
2026-03-19 8:58 ` Krzysztof Kozlowski
2026-03-31 7:10 ` Wolfram Sang
2026-03-31 7:14 ` Krzysztof Kozlowski
2026-03-31 7:40 ` Wolfram Sang
2026-03-31 7:52 ` Krzysztof Kozlowski
2026-03-31 7:18 ` Krzysztof Kozlowski [this message]
2026-03-31 7:33 ` Wolfram Sang
2026-03-19 9:15 ` Wolfram Sang
2026-03-18 9:17 ` Krzysztof Kozlowski
2026-03-19 8:58 ` Geert Uytterhoeven
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=28396df7-bb9f-4a6a-963c-0b56c66fb3cd@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox