From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Matt Ranostay <mranostay@ti.com>,
vigneshr@ti.com, robh@kernel.org, a.zummo@towertech.it,
linus.walleij@linaro.org, lee@kernel.org, brgl@bgdev.pl
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org,
Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH v4 2/4] MFD: TPS6594x: Add new PMIC device driver for TPS6594x chips
Date: Fri, 18 Nov 2022 11:23:05 +0100 [thread overview]
Message-ID: <966aa391-8a49-c64b-9985-3d50a8c35891@linaro.org> (raw)
In-Reply-To: <20221118092218.480147-3-mranostay@ti.com>
On 18/11/2022 10:22, Matt Ranostay wrote:
> From: Keerthy <j-keerthy@ti.com>
>
> The TPS6594x chip is a PMIC, and contains the following components:
No improvements in the subject. The subject prefixes are lowercase.
In the binding you said device is "TPS6594", not TPS6594x.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-18 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 9:22 [PATCH v4 0/4] mfd: add tps6594x support for Jacinto platforms Matt Ranostay
2022-11-18 9:22 ` [PATCH v4 1/4] Documentation: ti,tps6594: Add DT bindings for the TPS6594x PMIC Matt Ranostay
2022-11-18 10:21 ` Krzysztof Kozlowski
2022-11-19 4:23 ` Matt Ranostay
2022-11-18 13:31 ` Rob Herring
2022-11-18 9:22 ` [PATCH v4 2/4] MFD: TPS6594x: Add new PMIC device driver for TPS6594x chips Matt Ranostay
2022-11-18 10:23 ` Krzysztof Kozlowski [this message]
2022-11-19 4:17 ` Matt Ranostay
2022-11-18 9:22 ` [PATCH v4 3/4] rtc: rtc-tps6594x: Add support for TPS6594X PMIC RTC Matt Ranostay
2022-11-18 9:22 ` [PATCH v4 4/4] gpio: gpio-tps6594x: add GPIO support for TPS6594x PMIC Matt Ranostay
2022-11-28 18:08 ` Bartosz Golaszewski
2022-11-28 20:38 ` Linus Walleij
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=966aa391-8a49-c64b-9985-3d50a8c35891@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a.zummo@towertech.it \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mranostay@ti.com \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).