All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	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>,
	Julien Grall <julien.grall@arm.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] xen: add DEBUG_INFO Kconfig symbol
Date: Fri, 31 Aug 2018 10:38:54 +0200	[thread overview]
Message-ID: <20180831083854.GC20226@aepfle.de> (raw)
In-Reply-To: <20180831083216.gxvhuunogisdiinx@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 259 bytes --]

On Fri, Aug 31, Wei Liu wrote:

> But what is the difference between this and DEBUG anyway?

DEBUG_INFO is for gcc (-g), DEBUG is for Kconfig.
Adding a dependency to DEBUG may change behavior, not sure what the
expected outcome of always using '-g' is.

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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

  reply	other threads:[~2018-08-31  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  8:29 [PATCH v2] xen: add DEBUG_INFO Kconfig symbol Olaf Hering
2018-08-31  8:32 ` Wei Liu
2018-08-31  8:38   ` Olaf Hering [this message]
2018-08-31  8:41   ` Jan Beulich
2018-08-31  8:51     ` Andrew Cooper
2018-08-31  8:52       ` Wei Liu
2018-08-31  8:43 ` Jan Beulich
2018-08-31  9:02   ` Olaf Hering
2018-08-31  9:25     ` Jan Beulich
2018-08-31  9:50       ` Julien Grall
2018-08-31 10:40         ` Jan Beulich
2018-09-10 13:21   ` Jan Beulich
2018-09-10 13:29     ` Jan Beulich
2018-09-10 17:51       ` Andrew Cooper
2018-09-11  7:58         ` 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=20180831083854.GC20226@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --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 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.