From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] build: move setting LTO options to xen/Rules.mk
Date: Fri, 23 Dec 2016 12:25:43 +0000 [thread overview]
Message-ID: <20161223122543.GU28690@citrix.com> (raw)
In-Reply-To: <1482495858-4334-3-git-send-email-wei.liu2@citrix.com>
On Fri, Dec 23, 2016 at 12:24:17PM +0000, Wei Liu wrote:
> Having them in StdGNU.mk would affect both hypervisor and tools build.
> However judging from the commit message of e4cdd74f LTO was only meant
> to affect hypvervisor build.
>
> Move the relevant bits to xen/Rules.mk.
>
Ah, git send-email *.patch -- please ignore this patch in this series.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-23 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 12:24 [PATCH v2 0/2] build: minor adjustment Wei Liu
2016-12-23 12:24 ` [PATCH v2 1/2] build: move debug{, _symbols} to tools/Rules.mk Wei Liu
2017-01-03 9:06 ` Jan Beulich
2016-12-23 12:24 ` [PATCH v2] build: move setting LTO options to xen/Rules.mk Wei Liu
2016-12-23 12:25 ` Wei Liu [this message]
2016-12-23 12:24 ` [PATCH v2 2/2] build: use debug_symbols to add -g3 Wei Liu
2017-01-03 9:07 ` Jan Beulich
2017-01-05 15:14 ` Wei Liu
2017-01-05 16:27 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2016-12-23 12:12 [PATCH v2] build: move setting LTO options to xen/Rules.mk Wei Liu
2017-01-05 15:09 ` Wei Liu
2017-01-05 15:23 ` Andrew Cooper
2017-01-05 15:37 ` Jan Beulich
2017-01-05 16:15 ` Ian Jackson
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=20161223122543.GU28690@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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).