From: "Jan Beulich" <JBeulich@suse.com>
To: Doug Goldstein <cardoe@cardoe.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 1/7] build: add debug menu to Kconfig
Date: Tue, 03 May 2016 09:18:53 -0600 [thread overview]
Message-ID: <5728DD7D02000078000E82B8@prv-mh.provo.novell.com> (raw)
In-Reply-To: <5728BF7C.6070102@citrix.com>
>>> On 03.05.16 at 17:10, <andrew.cooper3@citrix.com> wrote:
> On 03/05/16 16:05, Jan Beulich wrote:
>>>>> On 03.05.16 at 16:29, <cardoe@cardoe.com> wrote:
>>> --- /dev/null
>>> +++ b/xen/Kconfig.debug
>>> @@ -0,0 +1,7 @@
>>> +
>>> +menuconfig DEBUG
>>> + bool "Debugging Options"
>> One more thing: In the unstable branch this should really default to
>> y, and the release check list should be adjusted to say that this
>> default needs to be dropped (or inverted) while preparing a release.
>>
>> And obviously the "debug=" also needs to go away from ./Config.mk.
>
> Things other than Xen make use of debug= in the root Config.mk.
> Valgrind client requests for example in libxc.
>
> That option can't be moved without providing an alternative.
Why can't it be moved into tools/ if that's where it is still of interest?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-03 15:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 14:29 [PATCH v2 0/7] Kconfig debug options Doug Goldstein
2016-05-03 14:29 ` [PATCH v2 1/7] build: add debug menu to Kconfig Doug Goldstein
2016-05-03 14:38 ` Jan Beulich
2016-05-03 14:39 ` Doug Goldstein
2016-05-03 15:05 ` Jan Beulich
2016-05-03 15:10 ` Andrew Cooper
2016-05-03 15:18 ` Jan Beulich [this message]
2016-05-04 2:22 ` Doug Goldstein
2016-05-04 7:17 ` Jan Beulich
2016-05-03 14:29 ` [PATCH v2 2/7] build: convert crash_debug " Doug Goldstein
2016-05-03 14:43 ` Jan Beulich
2016-05-03 14:48 ` Doug Goldstein
2016-05-03 15:19 ` Jan Beulich
2016-05-04 3:10 ` Doug Goldstein
2016-05-04 7:20 ` Jan Beulich
2016-05-03 14:47 ` Andrew Cooper
2016-05-03 15:02 ` Jan Beulich
2016-05-03 14:29 ` [PATCH v2 3/7] build: convert verbose " Doug Goldstein
2016-05-03 14:47 ` Jan Beulich
2016-05-03 14:29 ` [PATCH v2 4/7] build: convert frame_pointer " Doug Goldstein
2016-05-03 14:49 ` Jan Beulich
2016-05-03 14:29 ` [PATCH v2 5/7] build: wire up pre-existing debug build flag Doug Goldstein
2016-05-03 14:50 ` Jan Beulich
2016-05-04 3:13 ` Doug Goldstein
2016-05-03 14:29 ` [PATCH v2 6/7] build: convert perfc{, _arrays} to Kconfig Doug Goldstein
2016-05-03 14:57 ` Jan Beulich
2016-05-03 14:29 ` [PATCH v2 7/7] build: convert lock_profile " Doug Goldstein
2016-05-03 14:59 ` Jan Beulich
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=5728DD7D02000078000E82B8@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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).