All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: drivers/clk/microchip/clk-core.c:915:10: sparse: sparse: Initializer entry defined twice
Date: Tue, 25 Nov 2025 14:42:47 -0500	[thread overview]
Message-ID: <aSYGt5O2PzqfKs_n@redhat.com> (raw)
In-Reply-To: <202511222115.uvHrP95A-lkp@intel.com>

On Sat, Nov 22, 2025 at 09:39:06PM +0800, kernel test robot wrote:
> Hi Brian,
> 
> First bad commit (maybe != root cause):
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   2eba5e05d9bcf4cdea995ed51b0f07ba0275794a
> commit: 7d85cd8730ab7701a1cafd0db0d7b6b1f6cfbb91 clk: microchip: core: remove duplicate roclk_determine_rate()
> date:   7 weeks ago
> config: mips-randconfig-r134-20251122 (https://download.01.org/0day-ci/archive/20251122/202511222115.uvHrP95A-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9e9fe08b16ea2c4d9867fb4974edf2a3776d6ece)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251122/202511222115.uvHrP95A-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202511222115.uvHrP95A-lkp@intel.com/
> 
> sparse warnings: (new ones prefixed by >>)
> >> drivers/clk/microchip/clk-core.c:915:10: sparse: sparse: Initializer entry defined twice
>    drivers/clk/microchip/clk-core.c:919:10: sparse:   also defined here
> 
> vim +915 drivers/clk/microchip/clk-core.c
> 
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  910  
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  911  /* sclk with post-divider */
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  912  const struct clk_ops pic32_sclk_ops = {
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  913  	.get_parent	= sclk_get_parent,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  914  	.set_parent	= sclk_set_parent,
> e9f039c08cdc9b Brian Masney         2025-08-11 @915  	.determine_rate = sclk_determine_rate,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  916  	.set_rate	= sclk_set_rate,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  917  	.recalc_rate	= sclk_get_rate,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  918  	.init		= sclk_init,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  919  	.determine_rate = __clk_mux_determine_rate,
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  920  };
> ce6e1188465998 Purna Chandra Mandal 2016-05-13  921  
> 
> :::::: The code at line 915 was first introduced by commit
> :::::: e9f039c08cdc9b38665aee9a88ae21f59c09ba8c clk: microchip: core: convert from round_rate() to determine_rate()
> 
> :::::: TO: Brian Masney <bmasney@redhat.com>
> :::::: CC: Brian Masney <bmasney@redhat.com>

Thanks for the report. I posted a fix for this:

https://lore.kernel.org/linux-clk/20251125-clk-microchip-fixes-v1-0-6c1f5573d1b9@redhat.com/T/#t

Brian


  reply	other threads:[~2025-11-25 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22 13:39 drivers/clk/microchip/clk-core.c:915:10: sparse: sparse: Initializer entry defined twice kernel test robot
2025-11-25 19:42 ` Brian Masney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-06 21:52 kernel test robot
2026-01-08 23:17 ` Brian Masney

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=aSYGt5O2PzqfKs_n@redhat.com \
    --to=bmasney@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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.