From: Brian Masney <bmasney@redhat.com>
To: Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] clk: st: clkgen-pll: Rename clk variable in clkgen_c32_pll_setup()
Date: Thu, 22 Jan 2026 18:37:00 -0500 [thread overview]
Message-ID: <aXK0nJojFrDMWVm3@redhat.com> (raw)
In-Reply-To: <20260121012223.186199-4-lihaoxiang@isrc.iscas.ac.cn>
On Wed, Jan 21, 2026 at 09:22:19AM +0800, Haoxiang Li wrote:
> In clkgen_c32_pll_setup(), `clk` is used for two distint variables' name.
> This patch rename the later `clk` to `odf_clk`.
> The rename is in preparation for cleaning up some memory leaks.
>
> Signed-off-by: Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>
Reviewed-by: Brian Masney <bmasney@redhat.com>
next prev parent reply other threads:[~2026-01-22 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 1:22 [PATCH v2 0/7] clk: st: clkgen-pll: Add cleanup in clkgen_c32_pll_setup() and clkgen_odf_register() Haoxiang Li
2026-01-21 1:22 ` [PATCH v2 1/7] clk: st: clkgen-pll: Fix a memory leak in clkgen_odf_register() Haoxiang Li
2026-01-21 9:30 ` Markus Elfring
2026-01-21 1:22 ` [PATCH v2 2/7] clk: st: clkgen-pll: Rename clk variable in clkgen_c32_pll_setup() Haoxiang Li
2026-01-21 9:41 ` Markus Elfring
2026-01-21 1:22 ` [PATCH v2 3/7] " Haoxiang Li
2026-01-21 9:48 ` Markus Elfring
2026-01-22 23:37 ` Brian Masney [this message]
2026-01-21 1:22 ` [PATCH v2 4/7] clk: st: clkgen-pll: Add iounmap() " Haoxiang Li
2026-01-21 10:03 ` Markus Elfring
2026-01-21 1:22 ` [PATCH v2 5/7] clk: st: clkgen-pll: Add clk_unregister for pll_clk " Haoxiang Li
2026-01-21 1:22 ` [PATCH v2 6/7] clk: st: clkgen-pll: Remove redundant kfree() " Haoxiang Li
2026-01-21 1:22 ` [PATCH v2 7/7] clk: st: clkgen-pll: Add clk_unregister for odf_clk " Haoxiang Li
2026-01-21 10:15 ` Markus Elfring
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=aXK0nJojFrDMWVm3@redhat.com \
--to=bmasney@redhat.com \
--cc=lihaoxiang@isrc.iscas.ac.cn \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.