From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Kevin Tian <kevin.tian@intel.com>,
Feng Wu <feng.wu@intel.com>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] xen: remove dups in x86 and x86_64 variables
Date: Wed, 23 Dec 2015 19:29:41 +0000 [thread overview]
Message-ID: <567AF625.9080701@citrix.com> (raw)
In-Reply-To: <1450898123-487-1-git-send-email-cardoe@cardoe.com>
On 23/12/2015 19:15, Doug Goldstein wrote:
> Currently the Xen build uses x86 and x86_64 variables as well as
> CONFIG_X86 and CONFIG_X86_64. This just removes the duplication. The
> CONFIG_ variables are now managed by Kconfig but existed previously so
> this duplication existed prior to the Kconfig migration.
>
> Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2015-12-23 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 19:15 [PATCH] xen: remove dups in x86 and x86_64 variables Doug Goldstein
2015-12-23 19:29 ` Andrew Cooper [this message]
2015-12-24 0:59 ` Wu, Feng
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=567AF625.9080701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=feng.wu@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.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 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.