From: Lee Jones <lee@kernel.org>
To: 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,
Shree Ramamoorthy <s-ramamoorthy@ti.com>
Cc: m-leonard@ti.com, praneeth@ti.com, afd@ti.com
Subject: Re: [PATCH 0/2] TI TPS65214 & TPS65215: Update MFD Cell Structs
Date: Thu, 19 Jun 2025 16:19:51 +0100 [thread overview]
Message-ID: <175034639178.919047.12885250485072078236.b4-ty@kernel.org> (raw)
In-Reply-To: <20250527190455.169772-1-s-ramamoorthy@ti.com>
On Tue, 27 May 2025 14:04:53 -0500, Shree Ramamoorthy wrote:
> The patches updates the GPIO compatible string for the TPS65214 & TPS65215
> MFD cell struct based on a system design change made after driver
> development. TPS65215 & TPS65219 now share the same GPIO count 2 GPOs and
> 1 GPIO), instead of TPS65214 & TPS65215. TPS65215 will reuse the TPS65219
> GPIO compatible string, instead of TPS65214. TPS65214 still has 1 GPO and
> 1 GPIO.
>
> [...]
Applied, thanks!
[1/2] mfd: tps65219: Update TPS65214 MFD cell's GPIO compatible string
commit: b2082f5eabe1a2e1a0746258cf9f88bc313d0b35
[2/2] mfd: tps65219: Update TPS65215's MFD cell GPIO compatible string
(no commit info)
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-06-19 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 19:04 Shree Ramamoorthy
2025-05-27 19:04 ` [PATCH 1/2] mfd: tps65219: Update TPS65214 MFD cell's GPIO compatible string Shree Ramamoorthy
2025-06-13 13:15 ` Lee Jones
2025-06-13 19:35 ` Shree Ramamoorthy
2025-06-13 13:26 ` (subset) " Lee Jones
2025-05-27 19:04 ` [PATCH 2/2] mfd: tps65219: Update TPS65215's MFD cell " Shree Ramamoorthy
2025-06-19 11:44 ` [PATCH 0/2] TI TPS65214 & TPS65215: Update MFD Cell Structs Lee Jones
2025-06-19 15:19 ` Lee Jones [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=175034639178.919047.12885250485072078236.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--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
all inboxes | Powered by JetHome®