public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org,
	Marek Vasut <marek.vasut@mailbox.org>,
	devicetree@vger.kernel.org,
	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>
Subject: Re: [PATCH v2 1/3] dt-bindings: soc: renesas: Document MFIS IP core
Date: Tue, 31 Mar 2026 10:08:28 +0200	[thread overview]
Message-ID: <acuA_CGZNrsdmXy0@shikoro> (raw)
In-Reply-To: <cfee8254-8573-4106-b71f-293073b64c89@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]


> You made the posting unnecessarily complicated - this patch went to my
> DT address, but the rest to non-DT. Why not using b4 which gets it
> correct without effort? Plus it gives you much more like changelog with
> lore links and trailers handling?

Switching to b4 is on my to-do list. I will give it a priority boost.

> So now I found the driver (in different place...) and indeed you use
> some of the constants, so this is an ABI. It was so easy in v1 to just
> point me to usage of the ABI when I asked how do you use this in Linux...

Well, IMO I pointed you to the ABI by sending v2. I still think this is
a valid choice, I understand that you would have liked it differently.

Back on topic: As I understand it, I will prepare v3 by adding interrupt
constraints, fix the indentation and use your DT address properly,
right? The ABI issue is resolved now?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-03-31  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 11:07 [PATCH v2 0/3] soc: renesas: add MFIS driver Wolfram Sang
2026-03-25 11:07 ` [PATCH v2 1/3] dt-bindings: soc: renesas: Document MFIS IP core Wolfram Sang
2026-03-26  9:03   ` Krzysztof Kozlowski
2026-03-27 11:42     ` Wolfram Sang
2026-03-31  7:15       ` Krzysztof Kozlowski
2026-03-31  7:50         ` Krzysztof Kozlowski
2026-03-31  8:08           ` Wolfram Sang [this message]
2026-03-31  8:11             ` Krzysztof Kozlowski
2026-03-25 11:07 ` [PATCH v2 2/3] soc: renesas: Add Renesas R-Car MFIS driver Wolfram Sang
2026-03-28  0:16   ` Marek Vasut
2026-03-25 11:07 ` [PATCH v2 3/3] soc: renesas: add X5H PRR support 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=acuA_CGZNrsdmXy0@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=marek.vasut@mailbox.org \
    --cc=robh@kernel.org \
    /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