From: Andrew Davis <afd@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: am654-serdes-ctrl: Add simple-mfd to compatible items
Date: Tue, 25 Jun 2024 17:23:22 -0500 [thread overview]
Message-ID: <c3f4a289-03b1-48a5-a3dd-7cb7ca594055@ti.com> (raw)
In-Reply-To: <7fbb62b3-cc71-4fa8-a0c4-fca558292c75@siemens.com>
On 6/25/24 2:46 PM, Jan Kiszka wrote:
> On 25.06.24 18:49, Andrew Davis wrote:
>> On 6/25/24 11:45 AM, Andrew Davis wrote:
>>> This node contains a child which is only probed if simple-mfd is in the
>>> compatible list. Add this here.
>>>
>>> Signed-off-by: Andrew Davis <afd@ti.com>
>>> ---
>>
>> This patch depends on https://www.spinics.net/lists/kernel/msg5253666.html
>>
>
> But is that patch already scheduled for 6.10 as well?
I don't think so.. But only [patch 2/2] from this series needs applied
back to 6.10 to fix the issue. This one [Patch 1/2] just removes a dts warning.
Andrew
>
> Jan
>
next prev parent reply other threads:[~2024-06-25 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 16:45 Andrew Davis
2024-06-25 16:45 ` [PATCH 2/2] arm64: dts: ti: k3-am65: Add simple-mfd compatible to SerDes control nodes Andrew Davis
2024-06-25 21:53 ` Jan Kiszka
2024-06-25 16:49 ` [PATCH 1/2] dt-bindings: soc: ti: am654-serdes-ctrl: Add simple-mfd to compatible items Andrew Davis
2024-06-25 19:46 ` Jan Kiszka
2024-06-25 22:23 ` Andrew Davis [this message]
2024-06-28 21:38 ` Rob Herring
2024-06-28 23:06 ` Andrew Davis
2024-06-28 21:39 ` Rob Herring (Arm)
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=c3f4a289-03b1-48a5-a3dd-7cb7ca594055@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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®