All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, tim@xen.org,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH for-4.8 2/2] Config.mk: fix comment for debug option
Date: Tue, 1 Nov 2016 16:56:49 +0000	[thread overview]
Message-ID: <20161101165649.GE30231@citrix.com> (raw)
In-Reply-To: <5818C5FD02000078000F2645@prv-mh.provo.novell.com>

On Tue, Nov 01, 2016 at 10:42:37AM -0600, Jan Beulich wrote:
> >>> Wei Liu <wei.liu2@citrix.com> 11/01/16 5:38 PM >>>
> >On Tue, Nov 01, 2016 at 10:33:54AM -0600, Jan Beulich wrote:
> >> >>> Wei Liu <wei.liu2@citrix.com> 11/01/16 5:20 PM >>>
> >> >On Tue, Nov 01, 2016 at 10:18:46AM -0600, Jan Beulich wrote:
> >> >> >>> Wei Liu <wei.liu2@citrix.com> 11/01/16 2:48 PM >>>
> >> >> >config/StdGNU.mk | 8 --------
> >> >> >config/SunOS.mk  | 7 -------
> >> >> >tools/Rules.mk   | 4 +++-
> >> >> >xen/Rules.mk     | 6 ++++++
> >> >> >4 files changed, 9 insertions(+), 16 deletions(-)
> >> >> 
> >> >> Considering this diffstat - did the original global settings not get inherited
> >> >> by any of the other subtrees, namely stubdom/ and/or extras/ ?
> >> > 
> >> >I mentioned this in commit message and deliberately made the decision to
> >> >not inherit these flags for stubdom build.
> >> 
> >> Indeed, I've overlooked that part, but I'm not fully convinced. And then
> >
> >Not fully convinced because? Can you be more specific?
> 
> I don't know very much about the stubdom build machinery, but I could
> easily imaging some top level setting to have made it through to some
> of the sub-components, in which case this change would have a
> functional impact.
> 

I don't feel strongly about this. I can move some flags into stubdom
build system as well, just to err on the safe side.

Wei.

> Jan
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-01 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 17:09 [PATCH for-4.8 0/2] Disable debug build for hypervisor Wei Liu
2016-10-31 17:09 ` [PATCH for-4.8 1/2] xen: disable debug build Wei Liu
2016-10-31 17:09 ` [PATCH for-4.8 2/2] Config.mk: fix comment for debug option Wei Liu
2016-11-01 13:47   ` Wei Liu
2016-11-01 14:58     ` Andrew Cooper
2016-11-01 15:10       ` Wei Liu
2016-11-01 16:18     ` Jan Beulich
2016-11-01 16:20       ` Wei Liu
2016-11-01 16:33         ` Jan Beulich
2016-11-01 16:37           ` Wei Liu
2016-11-01 16:42             ` Jan Beulich
2016-11-01 16:56               ` Wei Liu [this message]
2016-11-01 16:56     ` Ian Jackson
2016-11-01 16:58       ` Andrew Cooper
2016-11-01 18:05       ` [OSSTEST PATCH] ts-xen-build: set CONFIG_DEBUG for KConfig Wei Liu
2016-11-01 18:08         ` Ian Jackson
2016-10-31 17:11 ` [PATCH for-4.8 0/2] Disable debug build for hypervisor Andrew Cooper
2016-10-31 17:23   ` Jan Beulich
2016-10-31 17:30   ` Konrad Rzeszutek Wilk

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=20161101165649.GE30231@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 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.