From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: qii.wang@mediatek.com
Cc: matthias.bgg@gmail.com, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, wsa@kernel.org,
Qii Wang <wii.wang@mediatek.com>
Subject: Re: [PATCH v2] i2c: busses: i2c-mt65xx: Simplify with clk-bulk
Date: Thu, 3 Mar 2022 10:25:22 +0100 [thread overview]
Message-ID: <22eccb9e-45fa-683e-640d-6f34fa63ca52@collabora.com> (raw)
In-Reply-To: <20220303091547.17522-1-angelogioacchino.delregno@collabora.com>
Il 03/03/22 10:15, AngeloGioacchino Del Regno ha scritto:
> Since depending on the SoC or specific bus functionality some clocks
> may be optional, we cannot get the benefit of using devm_clk_bulk_get()
> but, by migrating to clk-bulk, we are able to remove the custom functions
> mtk_i2c_clock_enable() and mtk_i2c_clock_disable(), increasing common
> APIs usage, hence (lightly) decreasing kernel footprint.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Reviewed-by: Qii Wang <wii.wang@mediatek.com>
> ---
>
> v2: Rebased on top of wsa/linux.git branch i2c/for-mergewindow
>
> drivers/i2c/busses/i2c-mt65xx.c | 124 +++++++++++++-------------------
> 1 file changed, 51 insertions(+), 73 deletions(-)
>
Hello Wolfram,
I'm sorry but in this v2 I have typoed Qii Wang's email
(qii.wang <at> mediatek.com).
Please, can you fix that while applying, or should I send a v3?
Sorry again and thank you,
Angelo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-03 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 9:15 [PATCH v2] i2c: busses: i2c-mt65xx: Simplify with clk-bulk AngeloGioacchino Del Regno
2022-03-03 9:25 ` AngeloGioacchino Del Regno [this message]
2022-03-03 12:02 ` Wolfram Sang
2022-03-11 20:35 ` 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=22eccb9e-45fa-683e-640d-6f34fa63ca52@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.com \
--cc=wii.wang@mediatek.com \
--cc=wsa@kernel.org \
/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