From: Wei Liu <wei.liu2@citrix.com>
To: Chris Patterson <cjp256@gmail.com>
Cc: ian.jackson@eu.citrix.com,
Chris Patterson <pattersonc@ainfosec.com>,
wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: compilation warning fix for arm & aarch64
Date: Mon, 1 Aug 2016 11:25:50 +0100 [thread overview]
Message-ID: <20160801102550.GM22419@citrix.com> (raw)
In-Reply-To: <20160728100941.GL27082@citrix.com>
On Thu, Jul 28, 2016 at 11:09:41AM +0100, Wei Liu wrote:
> On Wed, Jul 27, 2016 at 04:01:26PM -0400, Chris Patterson wrote:
> > From: Chris Patterson <pattersonc@ainfosec.com>
> >
> > GCC 6 will warn on unused static const variables in c modules:
> > https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00847.html
> >
> > When compiling with LIBXL_HAVE_NO_SUSPEND_RESUME set (arm & aarch64),
> > the compiler emits the following errors:
> > xl_cmdimpl.c:101:19: error: 'migrate_report'
> > defined but not used [-Werror=unused-const-variable=]
> > xl_cmdimpl.c:99:19: error: 'migrate_permission_to_go'
> > defined but not used [-Werror=unused-const-variable=]
> > xl_cmdimpl.c:97:19: error: 'migrate_receiver_ready'
> > defined but not used [-Werror=unused-const-variable=]
> > xl_cmdimpl.c:95:19: error: 'migrate_receiver_banner'
> > defined but not used [-Werror=unused-const-variable=]
> >
> > These unused const variables are only used in functions which exist between
> > the ifndef block:
> > #ifndef LIBXL_HAVE_NO_SUSPEND_RESUME
> > ...
> > #endif
> >
> > Wrap the same ifndef around these variables.
> >
> > Signed-off-by: Chris Patterson <pattersonc@ainfosec.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
>
Pushed.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-08-01 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 20:01 [PATCH] libxl: compilation warning fix for arm & aarch64 Chris Patterson
2016-07-28 10:09 ` Wei Liu
2016-08-01 10:25 ` Wei Liu [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=20160801102550.GM22419@citrix.com \
--to=wei.liu2@citrix.com \
--cc=cjp256@gmail.com \
--cc=ian.jackson@eu.citrix.com \
--cc=pattersonc@ainfosec.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.