mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Ward <Adam.Ward.opensource@diasemi.com>
To: Zou Wei <zou_wei@huawei.com>,
	Support Opensource <Support.Opensource@diasemi.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"broonie@kernel.org" <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH -next] regulator: da9121: Mark some symbols with static keyword
Date: Thu, 3 Dec 2020 14:37:48 +0000	[thread overview]
Message-ID: <AM6PR10MB2807AEED4498B051B227E7D8ECF20@AM6PR10MB2807.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1606994795-36182-1-git-send-email-zou_wei@huawei.com>

Acked-by: Adam Ward <Adam.Ward.opensource@diasemi.com>

> -----Original Message-----
> From: Zou Wei <zou_wei@huawei.com>
> Sent: 03 December 2020 11:27
> To: Support Opensource <Support.Opensource@diasemi.com>;
> lgirdwood@gmail.com; broonie@kernel.org
> Cc: linux-kernel@vger.kernel.org; Zou Wei <zou_wei@huawei.com>
> Subject: [PATCH -next] regulator: da9121: Mark some symbols with static
> keyword
> 
> Fix the following sparse warnings:
> 
> drivers/regulator/da9121-regulator.c:55:21: warning: symbol
> 'da9121_10A_2phase_current' was not declared. Should it be static?
> drivers/regulator/da9121-regulator.c:63:21: warning: symbol
> 'da9121_6A_2phase_current' was not declared. Should it be static?
> drivers/regulator/da9121-regulator.c:71:21: warning: symbol
> 'da9121_5A_1phase_current' was not declared. Should it be static?
> drivers/regulator/da9121-regulator.c:79:21: warning: symbol
> 'da9121_3A_1phase_current' was not declared. Should it be static?
> drivers/regulator/da9121-regulator.c:151:32: warning: symbol
> 'status_event_handling' was not declared. Should it be static?
> 
> Signed-off-by: Zou Wei <zou_wei@huawei.com>
> ---
>  drivers/regulator/da9121-regulator.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/regulator/da9121-regulator.c b/drivers/regulator/da9121-
> regulator.c
> index 3ead6a1..893512c 100644
> --- a/drivers/regulator/da9121-regulator.c
> +++ b/drivers/regulator/da9121-regulator.c
> @@ -52,7 +52,7 @@ struct da9121_range {
>  	int reg_max;
>  };
> 
> -struct da9121_range da9121_10A_2phase_current = {
> +static struct da9121_range da9121_10A_2phase_current = {
>  	.val_min =  7000000,
>  	.val_max = 20000000,
>  	.val_stp =  1000000,
> @@ -60,7 +60,7 @@ struct da9121_range da9121_10A_2phase_current = {
>  	.reg_max = 14,
>  };
> 
> -struct da9121_range da9121_6A_2phase_current = {
> +static struct da9121_range da9121_6A_2phase_current = {
>  	.val_min =  7000000,
>  	.val_max = 12000000,
>  	.val_stp =  1000000,
> @@ -68,7 +68,7 @@ struct da9121_range da9121_6A_2phase_current = {
>  	.reg_max = 6,
>  };
> 
> -struct da9121_range da9121_5A_1phase_current = {
> +static struct da9121_range da9121_5A_1phase_current = {
>  	.val_min =  3500000,
>  	.val_max = 10000000,
>  	.val_stp =   500000,
> @@ -76,7 +76,7 @@ struct da9121_range da9121_5A_1phase_current = {
>  	.reg_max = 14,
>  };
> 
> -struct da9121_range da9121_3A_1phase_current = {
> +static struct da9121_range da9121_3A_1phase_current = {
>  	.val_min = 3500000,
>  	.val_max = 6000000,
>  	.val_stp =  500000,
> @@ -148,7 +148,7 @@ struct status_event_data {
>   *
>   * GPIO0/1/2 are not configured for use by default, so should not be seen.
>   */
> -const struct status_event_data status_event_handling[] = {
> +static const struct status_event_data status_event_handling[] = {
>  	DA9xxx_STATUS(0, 0, SG, 0, "Handled E_SG\n"),
>  	DA9121_STATUS(0, 0, TEMP_CRIT,
> (REGULATOR_EVENT_OVER_TEMP|REGULATOR_EVENT_DISABLE), NULL),
>  	DA9121_STATUS(0, 0, TEMP_WARN,
> REGULATOR_EVENT_OVER_TEMP, NULL),
> --
> 2.6.2


  reply	other threads:[~2020-12-03 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 11:26 Zou Wei
2020-12-03 14:37 ` Adam Ward [this message]
2020-12-03 15:46 ` Mark Brown

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=AM6PR10MB2807AEED4498B051B227E7D8ECF20@AM6PR10MB2807.EURPRD10.PROD.OUTLOOK.COM \
    --to=adam.ward.opensource@diasemi.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zou_wei@huawei.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

all inboxes | Powered by JetHome®