From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>, Stefan Roese <sr@denx.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH 08/15] i2c: busses: mt7621: Use devm_clk_get_enabled()
Date: Fri, 23 Jun 2023 11:55:30 +0200 [thread overview]
Message-ID: <ZJVsEp+cQZruztr0@shikoro> (raw)
In-Reply-To: <20230611225702.891856-9-andi.shyti@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
On Mon, Jun 12, 2023 at 12:56:55AM +0200, Andi Shyti wrote:
> Replace the pair of functions, devm_clk_get() and
> clk_prepare_enable(), with a single function
> devm_clk_get_enabled().
>
> Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
> Cc: Stefan Roese <sr@denx.de>
> Cc: Matthias Brugger <matthias.bgg@gmail.com>
> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-23 9:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 22:56 [PATCH 00/15] i2c: busses: Use devm_clk_get_enabled() Andi Shyti
2023-06-11 22:56 ` [PATCH 01/15] i2c: busses: emev2: " Andi Shyti
2023-06-12 7:11 ` Geert Uytterhoeven
2023-06-12 7:54 ` Andi Shyti
2023-06-11 22:56 ` [PATCH 02/15] i2c: busses: xiic: " Andi Shyti
2023-06-12 8:07 ` Michal Simek
2023-06-23 9:54 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 03/15] i2c: busses: at91-core: " Andi Shyti
2023-06-23 10:23 ` Wolfram Sang
2023-06-23 14:21 ` Nicolas Ferre
2023-06-23 14:38 ` Nicolas Ferre
2023-10-21 18:35 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 04/15] i2c: busses: exynos5: " Andi Shyti
2023-06-23 10:03 ` Wolfram Sang
2023-06-23 11:48 ` Andi Shyti
2023-06-23 12:18 ` Krzysztof Kozlowski
2023-06-23 12:30 ` Andi Shyti
2023-06-23 12:29 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 05/15] i2c: busses: hix5hd2: " Andi Shyti
2023-06-23 10:09 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 06/15] i2c: busses: jz4780: " Andi Shyti
2023-06-23 10:15 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 07/15] i2c: busses: lpc2k: " Andi Shyti
2023-06-23 10:16 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 08/15] i2c: busses: mt7621: " Andi Shyti
2023-06-12 3:17 ` Matthias Brugger
2023-06-12 8:43 ` Stefan Roese
2023-06-23 9:55 ` Wolfram Sang [this message]
2023-06-11 22:56 ` [PATCH 09/15] i2c: busses: owl: " Andi Shyti
2023-06-23 10:19 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 10/15] i2c: busses: pasemi-platform: " Andi Shyti
2023-06-12 12:58 ` alyssa
2023-06-23 9:56 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 11/15] i2c: busses: stm32f4: " Andi Shyti
2023-10-23 8:12 ` Alain Volmat
2023-10-23 15:30 ` Wolfram Sang
2023-06-11 22:56 ` [PATCH 12/15] i2c: busses: stm32f7: " Andi Shyti
2023-10-23 8:13 ` Alain Volmat
2023-10-23 15:30 ` Wolfram Sang
2023-06-11 22:57 ` [PATCH 13/15] i2c: busses: sun6i-p2wi: " Andi Shyti
2023-06-12 18:19 ` Jernej Škrabec
2023-06-23 9:58 ` Wolfram Sang
2023-06-11 22:57 ` [PATCH 14/15] i2c: busses: uniphier-f: " Andi Shyti
2023-06-23 10:22 ` Wolfram Sang
2023-06-11 22:57 ` [PATCH 15/15] i2c: busses: uniphier: " Andi Shyti
2023-06-23 10:23 ` Wolfram Sang
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=ZJVsEp+cQZruztr0@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-i2c@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sr@denx.de \
/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