From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sriranjani P <sriranjani.p@samsung.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
lee@kernel.org, devicetree@vger.kernel.org,
alim.akhtar@samsung.com, pankaj.dubey@samsung.com,
ravi.patel@samsung.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: Add SYSREG nodes for FSD SoC
Date: Mon, 21 Nov 2022 13:31:29 +0100 [thread overview]
Message-ID: <d507f9ff-d170-dc3a-cb73-f00b8b04c6a5@linaro.org> (raw)
In-Reply-To: <20221121091118.48628-1-sriranjani.p@samsung.com>
On 21/11/2022 10:11, Sriranjani P wrote:
> FSD SoC has three sysreg nodes one in PERIC block and other two are in
> FSYS0 and FSYS1 block. This patch series add required DT binding and
> DT file modifications.
>
> Sriranjani P (2):
> dt-bindings: mfd: syscon: Add tesla compatibles found on FSD SoC
> arm64: dts: fsd: add sysreg device node
>
> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
> arch/arm64/boot/dts/tesla/fsd.dtsi | 15 +++++++++++++++
This does not CC necessary lists and folks, but that's MAINTAINERS or
get_maintainers.pl fault. I sent a patch for it.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-11-21 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221121090555epcas5p29c8c7de6dba38449aaf3357beb43432d@epcas5p2.samsung.com>
2022-11-21 9:11 ` [PATCH 0/2] arm64: dts: Add SYSREG nodes for FSD SoC Sriranjani P
[not found] ` <CGME20221121090622epcas5p4cbce7d07007fc76d3c69e0013d3c4cf4@epcas5p4.samsung.com>
2022-11-21 9:11 ` [PATCH 1/2] dt-bindings: mfd: syscon: Add tesla compatibles found on " Sriranjani P
2022-11-21 12:25 ` Lee Jones
2022-11-23 12:02 ` Sriranjani P
[not found] ` <CGME20221121090647epcas5p439dc84f0c4f435a703a1f8396a11202f@epcas5p4.samsung.com>
2022-11-21 9:11 ` [PATCH 2/2] arm64: dts: fsd: add sysreg device node Sriranjani P
2022-11-21 12:27 ` Krzysztof Kozlowski
2022-11-23 11:57 ` Sriranjani P
2022-11-23 13:12 ` Krzysztof Kozlowski
2022-11-23 13:40 ` Sriranjani P
2022-11-24 9:19 ` Krzysztof Kozlowski
2022-11-21 12:31 ` Krzysztof Kozlowski [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=d507f9ff-d170-dc3a-cb73-f00b8b04c6a5@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.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;
as well as URLs for NNTP newsgroup(s).