From: "Jan Beulich" <JBeulich@suse.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [RFC PATCH 1/2] build: add debug menu to Kconfig
Date: Fri, 08 Apr 2016 17:18:06 -0600 [thread overview]
Message-ID: <57084A3E02000078000E6264@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1458838099-12053-1-git-send-email-cardoe@cardoe.com>
>>> On 24.03.16 at 17:48, <cardoe@cardoe.com> wrote:
> There are a number of debugging options for Xen so the idea is to have a
> menu to group them all together.
>
> Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
> ---
> This is more of an RFC than a merge request. If this seems reasonable I'll
> add all the other debugging options under this menu as well. Obviously if
> this seems reasonable and the patch is fine we can merge it and I'll submit
> the others as a follow up.
I certainly welcome this, provided a solution to the so far shared
meaning of "debug=y" for the xen/ and tools/ subtrees can be
found. Allowing them to use different settings is maybe a nice
option, but by default the build mode for both subtrees should
imo be the same.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-08 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 16:48 [RFC PATCH 1/2] build: add debug menu to Kconfig Doug Goldstein
2016-03-24 16:48 ` [RFC PATCH 2/2] build: convert crash_debug " Doug Goldstein
2016-03-25 19:49 ` Konrad Rzeszutek Wilk
2016-03-25 21:02 ` Doug Goldstein
2016-03-29 8:50 ` Jan Beulich
2016-03-30 15:38 ` Doug Goldstein
2016-04-08 23:24 ` Jan Beulich
2016-04-08 23:30 ` Jan Beulich
2016-03-25 19:42 ` [RFC PATCH 1/2] build: add debug menu " Konrad Rzeszutek Wilk
2016-03-25 20:59 ` Doug Goldstein
2016-03-30 15:29 ` Dario Faggioli
2016-04-08 23:18 ` Jan Beulich [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=57084A3E02000078000E6264@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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 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).