From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/acpi-processor: fix sparse warning
Date: Thu, 5 Feb 2015 14:31:04 -0500 [thread overview]
Message-ID: <20150205193104.GB11646@x230.dumpdata.com> (raw)
In-Reply-To: <1423136361-11338-1-git-send-email-prabhakar.csengg@gmail.com>
On Thu, Feb 05, 2015 at 11:39:21AM +0000, Lad Prabhakar wrote:
> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
>
> this patch fixes following sparse warning:
>
> xen-acpi-processor.c:505:23: warning: symbol 'xen_acpi_processor_resume_nb' was not declared. Should it be static?
Not sure if it is worth fixing it - as that whole code is only
executed under normal PV guests - where it does not make
sense for it be executed.
That whole xen_resume_notifier should go away.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> ---
> Found this issue on linux-next (gcc version 4.9.2,
> sparse version 0.4.5-rc1)and applies on top linux-next.
>
> drivers/xen/xen-acpi-processor.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/xen/xen-acpi-processor.c b/drivers/xen/xen-acpi-processor.c
> index 59fc190..6c1f921 100644
> --- a/drivers/xen/xen-acpi-processor.c
> +++ b/drivers/xen/xen-acpi-processor.c
> @@ -502,7 +502,7 @@ static int xen_acpi_processor_resume(struct notifier_block *nb,
> return xen_upload_processor_pm_data();
> }
>
> -struct notifier_block xen_acpi_processor_resume_nb = {
> +static struct notifier_block xen_acpi_processor_resume_nb = {
> .notifier_call = xen_acpi_processor_resume,
> };
>
> --
> 1.9.1
>
prev parent reply other threads:[~2015-02-05 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 11:39 [PATCH] xen/acpi-processor: fix sparse warning Lad Prabhakar
2015-02-05 19:31 ` Konrad Rzeszutek Wilk [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=20150205193104.GB11646@x230.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=xen-devel@lists.xenproject.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