Linux clock framework development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yu-Chun Lin" <eleanor.lin@realtek.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v15 04/11] clk: realtek: Introduce common probe()
Date: Fri, 02 Oct 2026 09:14:44 +0000	[thread overview]
Message-ID: <20261002091444.B54641F00893@smtp.kernel.org> (raw)
In-Reply-To: <20261002074331.3066919-5-eleanor.lin@realtek.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] clk: realtek: aux_name in struct rtk_clk_desc is missing const qualifier
--

commit 70362e309c085cb7899e077d069e8a4a7e5719cc
Author: Cheng-Yu Lee <cylee12@realtek.com>

clk: realtek: Introduce common probe()

Add rtk_clk_probe() to set up the shared regmap, register clock hardware,
and add the clock provider. Additionally, if the "#reset-cells" property is
present, it creates and registers an auxiliary device.

> diff --git a/drivers/clk/realtek/clk-rtk-common.h b/drivers/clk/realtek/clk-rtk-common.h
> new file mode 100644
> index 0000000000000..de3f23120b539
> --- /dev/null
> +++ b/drivers/clk/realtek/clk-rtk-common.h
> @@ -0,0 +1,37 @@

[ ... ]

> +struct rtk_clk_desc {
> +	struct clk_hw_onecell_data *clk_data;
> +	struct rtk_clk_regmap **clks;
> +	size_t num_clks;
> +	char *aux_name;

[Severity: Low]
Would it be better for aux_name to be a const char pointer here?

Since this struct member is typically assigned string literals by caller
drivers, dropping the const qualifier exposes read-only memory to accidental
modification and could cause compiler warnings if compiled with
-Wwrite-strings.

> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002074331.3066919-1-eleanor.lin@realtek.com?part=4

  reply	other threads:[~2026-10-02  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  7:43 [PATCH v15 00/11] clk / reset: realtek: Add RTD1625 clock and reset support Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 01/11] dt-bindings: clock: Add Realtek RTD1625 Clock & Reset Controller Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 02/11] reset: Add Realtek basic reset support Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 03/11] reset: realtek: Add RTD1625 reset controller driver Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 04/11] clk: realtek: Introduce common probe() Yu-Chun Lin
2026-10-02  9:14   ` sashiko-bot [this message]
2026-10-02  7:43 ` [PATCH v15 05/11] clk: realtek: Add support for phase locked loops (PLLs) Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 06/11] clk: realtek: Add support for gate clock Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 07/11] clk: realtek: Add support for mux clock Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 08/11] clk: realtek: Add support for MMC-tuned PLL clocks Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 09/11] clk: realtek: Add RTD1625-CRT clock controller driver Yu-Chun Lin
2026-10-02  9:14   ` sashiko-bot
2026-10-02  7:43 ` [PATCH v15 10/11] clk: realtek: Add RTD1625-ISO " Yu-Chun Lin
2026-10-02  7:43 ` [PATCH v15 11/11] arm64: dts: realtek: Add clock support for RTD1625 Yu-Chun Lin

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=20261002091444.B54641F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eleanor.lin@realtek.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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