From: George Dunlap <george.dunlap@citrix.com>
To: Juergen Gross <jgross@suse.com>, <xen-devel@lists.xenproject.org>
Cc: "Kevin Tian" <kevin.tian@intel.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Jun Nakajima" <jun.nakajima@intel.com>, "Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v3 1/2] xen: put more code under CONFIG_CRASH_DEBUG
Date: Fri, 20 Dec 2019 14:09:59 +0000 [thread overview]
Message-ID: <3f4161b2-e979-cb89-fb78-53777d9ede26@citrix.com> (raw)
In-Reply-To: <20191219074209.17277-2-jgross@suse.com>
On 12/19/19 7:42 AM, Juergen Gross wrote:
> Some code is not needed with CONFIG_CRASH_DEBUG, so only include it if
> CONFIG_CRASH_DEBUG is defined.
>
> While at it remove CONFIG_HAS_GDBSX as it can easily be replaced by
> CONFIG_CRASH_DEBUG.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
In case you need it for sched.h:
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-20 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 7:42 [Xen-devel] [PATCH v3 0/2] xen: make more debugger support code conditional Juergen Gross
2019-12-19 7:42 ` [Xen-devel] [PATCH v3 1/2] xen: put more code under CONFIG_CRASH_DEBUG Juergen Gross
2019-12-20 12:52 ` Andrew Cooper
2019-12-20 12:57 ` Jürgen Groß
2019-12-20 14:09 ` George Dunlap [this message]
2019-12-19 7:42 ` [Xen-devel] [PATCH v3 2/2] xen: make gdbsx support configurable Juergen Gross
2019-12-20 12:42 ` [Xen-devel] [PATCH v3 0/2] xen: make more debugger support code conditional Andrew Cooper
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=3f4161b2-e979-cb89-fb78-53777d9ede26@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@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.