From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Cc: stefano.stabellini@citrix.com
Subject: Re: [PATCH v2 3/7] xen/arm: Warn when a device tree path will be re-used by Xen
Date: Thu, 1 Oct 2015 13:01:29 +0100 [thread overview]
Message-ID: <1443700889.11707.24.camel@citrix.com> (raw)
In-Reply-To: <1443543701-18389-4-git-send-email-julien.grall@citrix.com>
On Tue, 2015-09-29 at 17:21 +0100, Julien Grall wrote:
> Xen is unconditionally using certain device tree paths to create DOM0
> specific node (for instance /psci, /memory and /hypervisor).
>
> Print a warning message on the console to let the user know if we
> re-use one of these nodes.
>
> Note that the content of most of those is very common and they
> should have already been skipped via the compatible string or typer
Stray "r" at the end (fixable on commit)
> string. This warning is here to catch unusual device-tree and
> compatible string that we may not yet support in Xen.
>
> Signed-off-by: Julien Grall <julien.grall@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Should we consider using /xen-psci or something to avoid this conflict? Or
(worse IMHO) adding a -N until we find an unused path?
next prev parent reply other threads:[~2015-10-01 12:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:21 [PATCH v2 0/7] xen/arm: gic-v2: Detect automatically aliased GIC 400 Julien Grall
2015-09-29 16:21 ` [PATCH v2 1/7] xen/arm: gic: Make it clear the GIC node is passed to make_hwdom_dt_node Julien Grall
2015-09-29 16:21 ` [PATCH v2 2/7] xen/arm: Retrieve the correct number of cells when building dom0 DT Julien Grall
2015-10-01 11:57 ` Ian Campbell
2015-09-29 16:21 ` [PATCH v2 3/7] xen/arm: Warn when a device tree path will be re-used by Xen Julien Grall
2015-10-01 12:01 ` Ian Campbell [this message]
2015-10-01 12:39 ` Julien Grall
2015-09-29 16:21 ` [PATCH v2 4/7] xen/arm: vgic-v2: Drop cbase from arch_domain Julien Grall
2015-09-29 16:21 ` [PATCH v2 5/7] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT Julien Grall
2015-10-01 12:08 ` Ian Campbell
2015-10-01 12:43 ` Julien Grall
2015-10-01 12:54 ` Ian Campbell
2015-09-29 16:21 ` [PATCH v2 6/7] xen/arm: gic-v2: Automatically detect aliased GIC400 Julien Grall
2015-10-01 12:10 ` Ian Campbell
2015-09-29 16:21 ` [PATCH v2 7/7] xen/arm: platform: Drop the quirks callback Julien Grall
2015-09-29 16:55 ` Julien Grall
2015-10-01 12:10 ` Ian Campbell
2015-10-01 12:56 ` [PATCH v2 0/7] xen/arm: gic-v2: Detect automatically aliased GIC 400 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=1443700889.11707.24.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@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 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).