linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Liam Beguin <liambeguin@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v1 1/4] clk: lmk04832: declare variables as const when possible
Date: Thu, 08 Dec 2022 17:19:09 -0800	[thread overview]
Message-ID: <20221209011911.EACF1C433F0@smtp.kernel.org> (raw)
In-Reply-To: <20221120030257.531153-2-liambeguin@gmail.com>

Quoting Liam Beguin (2022-11-19 19:02:54)
> Fix the following warning reported by the kernel test robot.
> 
>         cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>         >> drivers/clk/clk-lmk04832.c:357:15: warning: Variable 'pll2_p' can be declared with const [constVariable]
>             unsigned int pll2_p[] = {8, 2, 2, 3, 4, 5, 6, 7};
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/all/202203312017.5YW13Jr4-lkp@intel.com/
> Signed-off-by: Liam Beguin <liambeguin@gmail.com>
> ---

Applied to clk-next

  reply	other threads:[~2022-12-09  1:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20  3:02 [PATCH v1 0/4] clk: lmk04832: fix minor warnings and syntax issues Liam Beguin
2022-11-20  3:02 ` [PATCH v1 1/4] clk: lmk04832: declare variables as const when possible Liam Beguin
2022-12-09  1:19   ` Stephen Boyd [this message]
2022-11-20  3:02 ` [PATCH v1 2/4] clk: lmk04832: drop unnecessary semicolons Liam Beguin
2022-12-09  1:19   ` Stephen Boyd
2022-11-20  3:02 ` [PATCH v1 3/4] clk: lmk04832: drop superfluous #include Liam Beguin
2022-12-09  1:19   ` Stephen Boyd
2022-11-20  3:02 ` [PATCH v1 4/4] clk: lmk04832: fix kernel-doc warnings Liam Beguin
2022-12-09  1:19   ` Stephen Boyd

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=20221209011911.EACF1C433F0@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=liambeguin@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mturquette@baylibre.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;
as well as URLs for NNTP newsgroup(s).