From: Xukai Wang <kingxukai@zohomail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Samuel Holland <samuel.holland@sifive.com>,
Troy Mitchell <TroyMitchell988@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH] clk: canaan: k230: Fix sparse warnings reported by LKP
Date: Sun, 24 May 2026 16:16:06 +0800 [thread overview]
Message-ID: <89885938-f126-4e1b-aedb-3edb2da5df2d@zohomail.com> (raw)
In-Reply-To: <20260523-punctual-backslid-712c06f0db61@spud>
On 2026/5/23 22:02, Conor Dooley wrote:
> On Sat, May 23, 2026 at 03:00:15PM +0800, Xukai Wang wrote:
>> On 2026/5/23 04:39, Conor Dooley wrote:
>>> On Fri, May 22, 2026 at 08:59:12PM +0800, Xukai Wang wrote:
>>>> Fix all sparse warnings detected during LKP randconfig testing:
>>>> - Replace plain integer 0 with NULL.
>>>> - Add static modifier to k230_plls and k230_pll_divs.
>>>>
>>>> Reported-by: kernel test robot <lkp@intel.com>
>>>> Closes: https://lore.kernel.org/oe-kbuild-all/202605220724.j4ZeM3KI-lkp@intel.com/
>>>> Signed-off-by: Xukai Wang <kingxukai@zohomail.com>
>>> Forgot to reply earlier, but I went and squashed this in.
>> Thanks Conor!
> I dunno if you saw my message about giving what I have in my
> branches a go, but if you could try what's in the riscv-soc-for-next
> branch, that'd be great. Just to make sure that I have all the bits in
> place.
I have successfully tested your riscv-soc-for-next branch on K230
hardware. The clock controller probes correctly, and clk_summary shows
all PLLs and clocks are running as expected.
--
Best regards,
Xukai Wang
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-05-24 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 9:29 [PATCH v12 0/3] riscv: canaan: Add support for K230 clock Xukai Wang
2026-04-25 9:29 ` [PATCH v12 1/3] dt-bindings: clock: Add Canaan K230 clock controller Xukai Wang
2026-04-25 9:29 ` [PATCH v12 2/3] clk: canaan: Add clock driver for Canaan K230 Xukai Wang
2026-04-25 9:29 ` [PATCH v12 3/3] riscv: dts: canaan: Add clock definition for K230 Xukai Wang
2026-04-26 15:48 ` [PATCH v12 0/3] riscv: canaan: Add support for K230 clock Xukai Wang
2026-04-26 15:49 ` Xukai Wang
2026-05-22 7:24 ` Conor Dooley
2026-05-22 12:59 ` [PATCH] clk: canaan: k230: Fix sparse warnings reported by LKP Xukai Wang
2026-05-22 20:39 ` Conor Dooley
2026-05-23 7:00 ` Xukai Wang
2026-05-23 14:02 ` Conor Dooley
2026-05-23 15:25 ` Xukai Wang
2026-05-24 8:16 ` Xukai Wang [this message]
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=89885938-f126-4e1b-aedb-3edb2da5df2d@zohomail.com \
--to=kingxukai@zohomail.com \
--cc=TroyMitchell988@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox