mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Scheller <d.scheller.oss@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][media-next] media: dvb-frontends/stv0910: make various local variables static
Date: Sat, 22 Jul 2017 12:59:53 +0200	[thread overview]
Message-ID: <20170722125953.362fe9c6@audiostation.wuest.de> (raw)
In-Reply-To: <20170721110635.23610-1-colin.king@canonical.com>

Am Fri, 21 Jul 2017 12:06:35 +0100
schrieb Colin King <colin.king@canonical.com>:

> From: Colin Ian King <colin.king@canonical.com>
> 
> The list stvlist and arrays padc_lookup, s1_sn_lookup and s2_sn_lookup
> do not need to be in global scope, so make them all static.
> 
> Cleans up a bunch of smatch warnings:
> symbol 'padc_lookup' was not declared. Should it be static?
> symbol 's1_sn_lookup' was not declared. Should it be static?
> symbol 's2_sn_lookup' was not declared. Should it be static?
> symbol 'stvlist' was not declared. Should it be static?
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Thanks,

Acked-by: Daniel Scheller <d.scheller@gmx.net>

> ---
>  drivers/media/dvb-frontends/stv0910.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/media/dvb-frontends/stv0910.c
> b/drivers/media/dvb-frontends/stv0910.c index
> 7e8a460449c5..bae1da3fdb2d 100644 ---
> a/drivers/media/dvb-frontends/stv0910.c +++
> b/drivers/media/dvb-frontends/stv0910.c @@ -34,7 +34,7 @@
>  #define BER_SRC_S    0x20
>  #define BER_SRC_S2   0x20
>  
> -LIST_HEAD(stvlist);
> +static LIST_HEAD(stvlist);
>  
>  enum receive_mode { RCVMODE_NONE, RCVMODE_DVBS, RCVMODE_DVBS2,
> RCVMODE_AUTO }; 
> @@ -207,7 +207,7 @@ static int write_shared_reg(struct stv *state,
> u16 reg, u8 mask, u8 val) return status;
>  }
>  
> -struct slookup s1_sn_lookup[] = {
> +static struct slookup s1_sn_lookup[] = {
>  	{   0,    9242  },  /*C/N=  0dB*/
>  	{   5,    9105  },  /*C/N=0.5dB*/
>  	{  10,    8950  },  /*C/N=1.0dB*/
> @@ -264,7 +264,7 @@ struct slookup s1_sn_lookup[] = {
>  	{  510,    425  }   /*C/N=51.0dB*/
>  };
>  
> -struct slookup s2_sn_lookup[] = {
> +static struct slookup s2_sn_lookup[] = {
>  	{  -30,  13950  },  /*C/N=-2.5dB*/
>  	{  -25,  13580  },  /*C/N=-2.5dB*/
>  	{  -20,  13150  },  /*C/N=-2.0dB*/
> @@ -327,7 +327,7 @@ struct slookup s2_sn_lookup[] = {
>  	{  510,    463  },  /*C/N=51.0dB*/
>  };
>  
> -struct slookup padc_lookup[] = {
> +static struct slookup padc_lookup[] = {
>  	{    0,  118000 }, /* PADC=+0dBm  */
>  	{ -100,  93600  }, /* PADC=-1dBm  */
>  	{ -200,  74500  }, /* PADC=-2dBm  */

Best regards,
Daniel Scheller
-- 
https://github.com/herrnst

      reply	other threads:[~2017-07-22 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 11:06 Colin King
2017-07-22 10:59 ` Daniel Scheller [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=20170722125953.362fe9c6@audiostation.wuest.de \
    --to=d.scheller.oss@gmail.com \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®