From: Ian Campbell <ian.campbell@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Cc: Wei Liu <wei.liu2@citrix.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] tools: always enable HAS_MEM_ACCESS
Date: Tue, 15 Dec 2015 12:11:16 +0000 [thread overview]
Message-ID: <1450181476.16856.150.camel@citrix.com> (raw)
In-Reply-To: <1449849611-4993-1-git-send-email-cardoe@cardoe.com>
On Fri, 2015-12-11 at 10:00 -0600, Doug Goldstein wrote:
> For all supported targets HAS_MEM_ACCESS is enabled so this drops the
> conditional and always makes it enabled. The goal here is to remove the
> setting in the top level config directory when kconfig changes land.
>
> Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
I suppose any future arch which doesn't initially add xen access support
will have to patch the Kconfig later on, which is fine by me.
> ---
> tools/tests/xen-access/Makefile | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/tools/tests/xen-access/Makefile b/tools/tests/xen-
> access/Makefile
> index f810543..dd70f9f 100644
> --- a/tools/tests/xen-access/Makefile
> +++ b/tools/tests/xen-access/Makefile
> @@ -7,8 +7,7 @@ CFLAGS += $(CFLAGS_libxenctrl)
> CFLAGS += $(CFLAGS_libxenguest)
> CFLAGS += $(CFLAGS_xeninclude)
>
> -TARGETS-y :=
> -TARGETS-$(HAS_MEM_ACCESS) := xen-access
> +TARGETS-y := xen-access
> TARGETS := $(TARGETS-y)
>
> .PHONY: all
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-15 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 16:00 [PATCH] tools: always enable HAS_MEM_ACCESS Doug Goldstein
2015-12-14 8:59 ` Jan Beulich
2015-12-14 11:44 ` Razvan Cojocaru
2015-12-15 12:11 ` Ian Campbell [this message]
2015-12-16 12:14 ` Ian Campbell
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=1450181476.16856.150.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tamas@tklengyel.com \
--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 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.