From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: <aaro.koskinen@iki.fi>, <andreas@kemnade.info>,
<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <m-leonard@ti.com>, <praneeth@ti.com>
Subject: [PATCH v1 0/4] TPS65219 Regulator Driver Cleanup Series
Date: Tue, 17 Dec 2024 14:45:22 -0600 [thread overview]
Message-ID: <20241217204526.1010989-1-s-ramamoorthy@ti.com> (raw)
This series is in preparation to add 2 PMIC devices to the TPS65219 driver.
The changes involve using dev_err_probe() for instances that have a chance
of returning -EPORBE_DEFER, remove redundant code, and follow other PMIC
regulator driver naming conventions. The intention is to remove unnecessary
noise from the new PMIC device patches added to this driver.
Shree Ramamoorthy (4):
regulator: tps65219: Use dev_err_probe() instead of dev_err()
regulator: tps65219: Update driver name
regulator: tps65219: Remove MODULE_ALIAS
regulator: tps65219: Remove debugging helper function
drivers/regulator/tps65219-regulator.c | 39 ++++----------------------
1 file changed, 5 insertions(+), 34 deletions(-)
--
2.34.1
next reply other threads:[~2024-12-17 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 20:45 Shree Ramamoorthy [this message]
2024-12-17 20:45 ` [PATCH v1 1/4] regulator: tps65219: Use dev_err_probe() instead of dev_err() Shree Ramamoorthy
2024-12-17 20:45 ` [PATCH v1 2/4] regulator: tps65219: Update driver name Shree Ramamoorthy
2024-12-17 21:01 ` Mark Brown
2024-12-17 21:16 ` Andrew Davis
2024-12-17 21:19 ` Mark Brown
2024-12-17 20:45 ` [PATCH v1 3/4] regulator: tps65219: Remove MODULE_ALIAS Shree Ramamoorthy
2024-12-17 20:45 ` [PATCH v1 4/4] regulator: tps65219: Remove debugging helper function Shree Ramamoorthy
2024-12-18 14:20 ` [PATCH v1 0/4] TPS65219 Regulator Driver Cleanup Series Mark Brown
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=20241217204526.1010989-1-s-ramamoorthy@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=khilman@baylibre.com \
--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=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
all inboxes | Powered by JetHome®