Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <lgirdwood@gmail.com>,
	<broonie@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <aaro.koskinen@iki.fi>,
	<andreas@kemnade.info>, <khilman@baylibre.com>,
	<rogerq@kernel.org>, <tony@atomide.com>, <lee@kernel.org>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Cc: <m-leonard@ti.com>, <praneeth@ti.com>
Subject: Re: [PATCH v6 2/9] regulator: dt-bindings: Add TI TPS65214 PMIC bindings
Date: Thu, 6 Mar 2025 16:58:48 -0600	[thread overview]
Message-ID: <d4e183c7-4ad6-4454-b854-8f1d64f296fa@ti.com> (raw)
In-Reply-To: <acea75f2-337e-4125-88d8-fbb07c8bf6c3@kernel.org>

Hi,

On 3/6/2025 1:25 AM, Krzysztof Kozlowski wrote:
> On 05/03/2025 22:03, Shree Ramamoorthy wrote:
>>  
>> @@ -102,7 +106,9 @@ allOf:
>>        properties:
>>          compatible:
>>            contains:
>> -            const: ti,tps65215
>> +            enum:
>> +              - ti,tps65214
>> +              - ti,tps65215
> I do not see improvements and you did not respond to my comment.
>
> Best regards,
> Krzysztof

Sorry for missing the enum fix, I thought I had included that and should've double checked.
Thank you again for reviewing these patches!


  reply	other threads:[~2025-03-06 22:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 21:03 [PATCH v6 0/9] Add TI TPS65214 & TPS65215 MFD & Regulator Support Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 1/9] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 2/9] regulator: dt-bindings: Add TI TPS65214 " Shree Ramamoorthy
2025-03-06  7:25   ` Krzysztof Kozlowski
2025-03-06 22:58     ` Shree Ramamoorthy [this message]
2025-03-05 21:03 ` [PATCH v6 3/9] mfd: tps65219: Remove regmap_read check Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 4/9] mfd: tps65219: Add support for TI TPS65215 PMIC Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 5/9] mfd: tps65219: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 6/9] regulator: tps65219: Update struct names Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 7/9] regulator: tps65219: Add support for TPS65215 regulator resources Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 8/9] regulator: tps65219: Add support for TPS65215 Regulator IRQs Shree Ramamoorthy
2025-03-05 21:03 ` [PATCH v6 9/9] regulator: tps65219: Add TI TPS65214 Regulator Support Shree Ramamoorthy
2025-03-06  7:27 ` [PATCH v6 0/9] Add TI TPS65214 & TPS65215 MFD & " Krzysztof Kozlowski

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=d4e183c7-4ad6-4454-b854-8f1d64f296fa@ti.com \
    --to=s-ramamoorthy@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m-leonard@ti.com \
    --cc=praneeth@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.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