From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] libxl: drop stray const from function return type
Date: Tue, 24 May 2016 16:44:08 +0100 [thread overview]
Message-ID: <20160524154408.GG22076@citrix.com> (raw)
In-Reply-To: <22340.30292.128116.109689@mariner.uk.xensource.com>
On Tue, May 24, 2016 at 04:42:12PM +0100, Ian Jackson wrote:
> Jan Beulich writes ("[PATCH] libxl: drop stray const from function return type"):
> > Some compiler versions warn about this, causing the build to fail due
> > to -Werror.
> >
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Queued.
Thank you both.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-05-24 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:28 [PATCH] libxl: drop stray const from function return type Jan Beulich
2016-05-24 15:42 ` Ian Jackson
2016-05-24 15:44 ` 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=20160524154408.GG22076@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.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;
as well as URLs for NNTP newsgroup(s).