From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Colin King <colin.king@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tim Sell <timothy.sell@unisys.com>,
David Binder <david.binder@unisys.com>,
Sameer Wadgaonkar <sameer.wadgaonkar@unisys.com>,
Charles Daniels <cdaniels@fastmail.com>,
sparmaintainer@unisys.com, devel@driverdev.osuosl.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][staging-next] staging: unisys: visorbus: make two functions static
Date: Fri, 01 Sep 2017 13:33:04 +0300 [thread overview]
Message-ID: <1504261984.25945.180.camel@linux.intel.com> (raw)
In-Reply-To: <20170901100810.17172-1-colin.king@canonical.com>
On Fri, 2017-09-01 at 11:08 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The functions sig_queue_offset and sig_data_offset are local to
> the source and do not need to be in global scope, so make them
> static.
>
> Cleans up sparse warnings:
> symbol 'sig_queue_offset' was not declared. Should it be static?
> symbol 'sig_data_offset' was not declared. Should it be static?
While patch below seems okay to me, I would recommend you to add
something like
--git-min-percent=67
to get_maintainer.pl command when you generate a list of people to whom
you Cc to.
Thanks for understanding.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/staging/unisys/visorbus/visorchannel.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/unisys/visorbus/visorchannel.c
> b/drivers/staging/unisys/visorbus/visorchannel.c
> index 49d1f5f9ef1d..2a000fee3119 100644
> --- a/drivers/staging/unisys/visorbus/visorchannel.c
> +++ b/drivers/staging/unisys/visorbus/visorchannel.c
> @@ -155,7 +155,7 @@ void *visorchannel_get_header(struct visorchannel
> *channel)
> * Return offset of a specific SIGNAL_QUEUE_HEADER from the beginning
> of a
> * channel header
> */
> -int sig_queue_offset(struct channel_header *chan_hdr, int q)
> +static int sig_queue_offset(struct channel_header *chan_hdr, int q)
> {
> return ((chan_hdr)->ch_space_offset +
> ((q) * sizeof(struct signal_queue_header)));
> @@ -165,8 +165,8 @@ int sig_queue_offset(struct channel_header
> *chan_hdr, int q)
> * Return offset of a specific queue entry (data) from the beginning
> of a
> * channel header
> */
> -int sig_data_offset(struct channel_header *chan_hdr, int q,
> - struct signal_queue_header *sig_hdr, int slot)
> +static int sig_data_offset(struct channel_header *chan_hdr, int q,
> + struct signal_queue_header *sig_hdr, int
> slot)
> {
> return (sig_queue_offset(chan_hdr, q) + sig_hdr-
> >sig_base_offset +
> (slot * sig_hdr->signal_size));
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-09-01 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 10:08 [PATCH][staging-next] staging: unisys: visorbus: make two functions static Colin King
2017-09-01 10:33 ` Andy Shevchenko [this message]
2017-09-01 21:56 ` Kershner, David A
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=1504261984.25945.180.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=cdaniels@fastmail.com \
--cc=colin.king@canonical.com \
--cc=david.binder@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameer.wadgaonkar@unisys.com \
--cc=sparmaintainer@unisys.com \
--cc=timothy.sell@unisys.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