From: Vignesh Raghavendra <vigneshr@ti.com>
To: Josua Mayer <josua@solid-run.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-rtc@vger.kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
Suman Anna <s-anna@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
MD Danish Anwar <danishanwar@ti.com>, Andrew Davis <afd@ti.com>
Subject: Re: [PATCH v5 0/5] arm64: dts: add description for solidrun am642 som and hummingboard evb
Date: Mon, 19 Feb 2024 09:52:18 +0530 [thread overview]
Message-ID: <bd93e51b-70ec-4cd4-88a3-1c79a0e3c75f@ti.com> (raw)
In-Reply-To: <c37af45e-def1-4a97-ae01-e00e5b22eb23@solid-run.com>
Hi,
On 18/02/24 19:48, Josua Mayer wrote:
> Am 13.02.24 um 07:12 schrieb Vignesh Raghavendra:
>> Hi
>>
>> [...]
>>
>> On 11/02/24 20:37, Josua Mayer wrote:
>>> ---
>>> Josua Mayer (4):
>>> dt-bindings: arm: ti: Add bindings for SolidRun AM642
>>> HummingBoard-T
This goes via TI K3 arch tree
>>
>>> dt-bindings: rtc: abx80x: convert to yaml
>>> dt-bindings: iio: humidity: hdc20x0: add optional interrupts
>>> property
>>> dt-bindings: mtd: spi-nor: add optional interrupts property
>> 2/5 needs to go via RTC subsystem tree. Could you split it out into its
>> own series when you respin
> Only rtc, or should I split out the other two as well?
Split others too. RTC, IIO and SPI-NOR related bindings should go via
respective trees. Please post them individually to appropriate lists.
Regards
Vignesh
prev parent reply other threads:[~2024-02-19 4:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 15:07 Josua Mayer
2024-02-11 15:07 ` [PATCH v5 1/5] dt-bindings: arm: ti: Add bindings for SolidRun AM642 HummingBoard-T Josua Mayer
2024-02-11 15:07 ` [PATCH v5 2/5] dt-bindings: rtc: abx80x: convert to yaml Josua Mayer
2024-02-11 16:22 ` Krzysztof Kozlowski
2024-02-11 15:07 ` [PATCH v5 3/5] arm64: dts: ti: k3-am64-main: Add ICSSG IEP nodes Josua Mayer
2024-02-11 15:07 ` [PATCH v5 4/5] arm64: dts: add description for solidrun am642 som and evaluation board Josua Mayer
2024-02-11 15:08 ` [PATCH v5 5/5] arm64: dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3 Josua Mayer
2024-02-12 4:10 ` [PATCH v5 0/5] arm64: dts: add description for solidrun am642 som and hummingboard evb Vignesh Raghavendra
2024-02-12 16:39 ` Josua Mayer
2024-02-12 16:58 ` Andrew Davis
2024-02-13 6:09 ` Vignesh Raghavendra
2024-02-13 6:12 ` Vignesh Raghavendra
2024-02-18 14:18 ` Josua Mayer
2024-02-19 4:22 ` Vignesh Raghavendra [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=bd93e51b-70ec-4cd4-88a3-1c79a0e3c75f@ti.com \
--to=vigneshr@ti.com \
--cc=a.zummo@towertech.it \
--cc=afd@ti.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=josua@solid-run.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=yazan.shhady@solid-run.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
all inboxes | Powered by JetHome®