Linux clock framework development
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-clk@vger.kernel.org, tsbogend@alpha.franken.de,
	sboyd@kernel.org, mturquette@baylibre.com,
	linux-kernel@vger.kernel.org, ndesaulniers@google.com,
	arnd@kernel.org, yangshiji66@outlook.com,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] clk: ralink: mtmips: quiet unused variable warning
Date: Tue, 17 Oct 2023 08:52:57 -0700	[thread overview]
Message-ID: <20231017155257.GA710773@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230827023932.501102-1-sergio.paracuellos@gmail.com>

On Sun, Aug 27, 2023 at 04:39:32AM +0200, Sergio Paracuellos wrote:
> When CONFIG_OF is disabled then the matching table is not referenced and
> the following warning appears:
> 
> drivers/clk/ralink/clk-mtmips.c:821:34: warning: unused variable 'mtmips_of_match' [-Wunused-const-variable]
> 821 |   static const struct of_device_id mtmips_of_match[] = {
>     |                          ^
> 
> There are two match tables in the driver: one for the clock driver and the
> other for the reset driver. The only difference between them is that the
> clock driver uses 'data' and does not have 'ralink,rt2880-reset' compatible.
> Both just can be merged into a single one just by adding the compatible
> 'ralink,rt2880-reset' entry to 'mtmips_of_match[]', which will allow it to
> be used for 'mtmips_clk_driver' (which doesn't use the data) as well as for
> 'mtmips_clk_init()' (which doesn't need get called for 'ralink,rt2880-reset').
> 
> Doing in this way ensures that 'CONFIG_OF' is not disabled anymore so the
> above warning disapears.
> 
> Fixes: 6f3b15586eef ("clk: ralink: add clock and reset driver for MTMIPS SoCs")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202307242310.CdOnd2py-lkp@intel.com/
> Suggested-by: Arnd Bergmann <arnd@kernel.org>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
> Changes in v2:
> - Merge two match tables into one to properly avoid this warning.
> 
> PATCH in v1: https://lore.kernel.org/lkml/20230802092647.3000666-1-sergio.paracuellos@gmail.com/T/
> 
>  drivers/clk/ralink/clk-mtmips.c | 20 +++++---------------
>  1 file changed, 5 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/clk/ralink/clk-mtmips.c b/drivers/clk/ralink/clk-mtmips.c
> index 1e7991439527..50a443bf79ec 100644
> --- a/drivers/clk/ralink/clk-mtmips.c
> +++ b/drivers/clk/ralink/clk-mtmips.c
> @@ -821,6 +821,10 @@ static const struct mtmips_clk_data mt76x8_clk_data = {
>  };
>  
>  static const struct of_device_id mtmips_of_match[] = {
> +	{
> +		.compatible = "ralink,rt2880-reset",
> +		.data = NULL,
> +	},
>  	{
>  		.compatible = "ralink,rt2880-sysc",
>  		.data = &rt2880_clk_data,
> @@ -1088,25 +1092,11 @@ static int mtmips_clk_probe(struct platform_device *pdev)
>  	return 0;
>  }
>  
> -static const struct of_device_id mtmips_clk_of_match[] = {
> -	{ .compatible = "ralink,rt2880-reset" },
> -	{ .compatible = "ralink,rt2880-sysc" },
> -	{ .compatible = "ralink,rt3050-sysc" },
> -	{ .compatible = "ralink,rt3052-sysc" },
> -	{ .compatible = "ralink,rt3352-sysc" },
> -	{ .compatible = "ralink,rt3883-sysc" },
> -	{ .compatible = "ralink,rt5350-sysc" },
> -	{ .compatible = "ralink,mt7620-sysc" },
> -	{ .compatible = "ralink,mt7628-sysc" },
> -	{ .compatible = "ralink,mt7688-sysc" },
> -	{}
> -};
> -
>  static struct platform_driver mtmips_clk_driver = {
>  	.probe = mtmips_clk_probe,
>  	.driver = {
>  		.name = "mtmips-clk",
> -		.of_match_table = mtmips_clk_of_match,
> +		.of_match_table = mtmips_of_match,
>  	},
>  };
>  
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2023-10-17 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27  2:39 [PATCH v2] clk: ralink: mtmips: quiet unused variable warning Sergio Paracuellos
2023-10-07  7:20 ` Sergio Paracuellos
2023-10-17 15:52 ` Nathan Chancellor [this message]
2023-10-18  8:59   ` Sergio Paracuellos
2023-10-19  0:32 ` Stephen Boyd
2023-10-19  4:10   ` Sergio Paracuellos

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=20231017155257.GA710773@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=arnd@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mturquette@baylibre.com \
    --cc=ndesaulniers@google.com \
    --cc=sboyd@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=yangshiji66@outlook.com \
    /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