From: Lee Jones <lee@kernel.org>
To: linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx
Date: Thu, 20 Nov 2025 14:18:29 +0000 [thread overview]
Message-ID: <176364830946.726067.14196845460912590375.b4-ty@kernel.org> (raw)
In-Reply-To: <20251117-aeration-smock-5e7ac06e2942@spud>
On Mon, 17 Nov 2025 16:29:29 +0000, Conor Dooley wrote:
> On pic64gx these syscons are identical to those on mpfs, and should use
> a fallback. Add support for multiple fallback compatibles to syscon.yaml
> with these as the first two users.
>
>
Applied, thanks!
[1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx
commit: 1f9793a4d5188cddc0eb69d7840b7c5c57c939a6
[2/2] dt-bindings: mfd: document syscons falling back to atmel,sama5d2-sfrbu
commit: 9494cb237b490cecc8c5d97824692b82097141c3
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-11-20 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:29 [PATCH 1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx Conor Dooley
2025-11-17 16:29 ` [PATCH 2/2] dt-bindings: mfd: document syscons falling back to atmel,sama5d2-sfrbu Conor Dooley
2025-11-17 22:45 ` Rob Herring (Arm)
2025-11-18 8:38 ` Nicolas Ferre
2025-11-17 22:44 ` [PATCH 1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx Rob Herring (Arm)
2025-11-20 14:18 ` Lee Jones [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=176364830946.726067.14196845460912590375.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nicolas.ferre@microchip.com \
--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