mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Baoyou Xie <baoyou.xie@linaro.org>, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linus.walleij@linaro.org, rob@kernel.org,
	maitysanchayan@gmail.com, leonard.crestez@intel.com,
	gregor.boirie@parrot.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, arnd@linaro.org,
	xie.baoyou@zte.com.cn
Subject: Re: [PATCH v2] fix:iio:common:st_sensors:st_sensors_trigger:mark symbols static where possible
Date: Mon, 29 Aug 2016 20:15:22 +0100	[thread overview]
Message-ID: <9bbf59e2-26e7-ee92-7568-4e1ecb990719@kernel.org> (raw)
In-Reply-To: <1472367851-14762-1-git-send-email-baoyou.xie@linaro.org>

On 28/08/16 08:04, Baoyou Xie wrote:
> We get 2 warnings when biuld kernel with W=1:
> drivers/iio/common/st_sensors/st_sensors_trigger.c:69:13: warning: no previous prototype
> for 'st_sensors_irq_handler' [-Wmissing-prototypes]
> drivers/iio/common/st_sensors/st_sensors_trigger.c:85:13: warning: no previous prototype
> for 'st_sensors_irq_thread' [-Wmissing-prototypes]
> 
> In fact, these functions are only used in the file in which they are
> declared and don't need a declaration, but can be made static.
> so this patch marks these functions with 'static'.
> 
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Hi.

Please don't resend just to add Reviewed-by / acked-by tags.
The maintainer will pick those up directly from the mailing list.

If there is anything else different here and I'm missing it you
should have highlighted what it was below the --- and
I'm really being unobservant!

Jonathan
> ---
>  drivers/iio/common/st_sensors/st_sensors_trigger.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/common/st_sensors/st_sensors_trigger.c b/drivers/iio/common/st_sensors/st_sensors_trigger.c
> index e66f12e..fa73e67 100644
> --- a/drivers/iio/common/st_sensors/st_sensors_trigger.c
> +++ b/drivers/iio/common/st_sensors/st_sensors_trigger.c
> @@ -66,7 +66,7 @@ static int st_sensors_new_samples_available(struct iio_dev *indio_dev,
>   * @irq: irq number
>   * @p: private handler data
>   */
> -irqreturn_t st_sensors_irq_handler(int irq, void *p)
> +static irqreturn_t st_sensors_irq_handler(int irq, void *p)
>  {
>  	struct iio_trigger *trig = p;
>  	struct iio_dev *indio_dev = iio_trigger_get_drvdata(trig);
> @@ -82,7 +82,7 @@ irqreturn_t st_sensors_irq_handler(int irq, void *p)
>   * @irq: irq number
>   * @p: private handler data
>   */
> -irqreturn_t st_sensors_irq_thread(int irq, void *p)
> +static irqreturn_t st_sensors_irq_thread(int irq, void *p)
>  {
>  	struct iio_trigger *trig = p;
>  	struct iio_dev *indio_dev = iio_trigger_get_drvdata(trig);
> 

      reply	other threads:[~2016-08-29 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28  7:04 Baoyou Xie
2016-08-29 19:15 ` Jonathan Cameron [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=9bbf59e2-26e7-ee92-7568-4e1ecb990719@kernel.org \
    --to=jic23@kernel.org \
    --cc=arnd@linaro.org \
    --cc=baoyou.xie@linaro.org \
    --cc=gregor.boirie@parrot.com \
    --cc=lars@metafoo.de \
    --cc=leonard.crestez@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maitysanchayan@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=rob@kernel.org \
    --cc=xie.baoyou@zte.com.cn \
    /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

Powered by JetHome