From: Roger Pau Monne <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH for-4.7] build: use C{C/XX} as HOSTC{C/XX} if we are not cross-compiling
Date: Thu, 28 Apr 2016 12:17:04 +0200 [thread overview]
Message-ID: <20160428101704.67quixw3j72txkns@mac> (raw)
In-Reply-To: <5721FD8A02000078000E6B84@prv-mh.provo.novell.com>
On Thu, Apr 28, 2016 at 04:09:46AM -0600, Jan Beulich wrote:
> >>> On 28.04.16 at 11:48, <roger.pau@citrix.com> wrote:
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> > ---
> > Config.mk | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/Config.mk b/Config.mk
> > index 9b097c9..67b26dd 100644
> > --- a/Config.mk
> > +++ b/Config.mk
> > @@ -45,6 +45,12 @@ DESTDIR ?= /
> > # Allow phony attribute to be listed as dependency rather than fake target
> > .PHONY: .phony
> >
> > +# If we are not cross-compiling, use C{C/XX} as HOSTC{C/XX}
>
> I think I'd prefer something like "..., default HOSTC{C/XX} to C{C/XX}"
> but apart from that (which could be adjusted while committing, if you
> agree)
> Acked-by: Jan Beulich <jbeulich@suse.com>
That's fine by me (and more accurate than my original message).
> (Side note: Please don't forget to Cc Wei on patches targeted at 4.7.
> And please don't forget to Cc relevant maintainers.)
Yes, my bad. I've actually forgotten to Cc anyone on this patch, sigh...
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-28 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:48 [PATCH for-4.7] build: use C{C/XX} as HOSTC{C/XX} if we are not cross-compiling Roger Pau Monne
2016-04-28 10:09 ` Jan Beulich
2016-04-28 10:17 ` Roger Pau Monne [this message]
2016-04-28 10:20 ` Wei Liu
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=20160428101704.67quixw3j72txkns@mac \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.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).