From: Dirk Behme <dirk.behme@gmail.com>
To: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Dirk Behme <dirk.behme@de.bosch.com>
Subject: Re: [PATCH] xen/arm: domain_build: DT: add clocks node to the hypervisor node
Date: Thu, 23 Jun 2016 17:59:18 +0200 [thread overview]
Message-ID: <576C0756.6080803@gmail.com> (raw)
In-Reply-To: <576BFA00.4060009@arm.com>
On 23.06.2016 17:02, Julien Grall wrote:
> On 22/06/16 16:58, Julien Grall wrote:
>> On 21/06/16 11:15, Dirk Behme wrote:
>>> + printk("Failed to remember the clock node of %s\n",
>>> path);
>>> + printk("Use the Linux kernel command
>>> 'clk_ignore_unused'\n");
>>> + return 0;
>>
>> I don't think this is tolerable. We need to fix it once and for all.
>>
>> I understand that xen does not provide a realloc function. Is there
>> another way we can get a rid of this limit?
>
> Note that I would wait that we agree on the device tree bindings
> before reworking this patch.
You mean the 'clocks' binding for the hypervisor node? I.e. as proposed in
https://lists.xen.org/archives/html/xen-devel/2016-06/msg02885.html
create a patch for
- linux/Documentation/devicetree/bindings/arm/xen.txt
- xen/docs/misc/arm/device-tree/guest.txt
and proceed only with the code changes when this is accepted?
Best regards
Dirk
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-23 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:15 [PATCH] xen/arm: domain_build: DT: add clocks node to the hypervisor node Dirk Behme
2016-06-21 10:20 ` Dirk Behme
2016-06-22 15:58 ` Julien Grall
2016-06-23 15:02 ` Julien Grall
2016-06-23 15:59 ` Dirk Behme [this message]
2016-06-23 16:02 ` Julien Grall
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=576C0756.6080803@gmail.com \
--to=dirk.behme@gmail.com \
--cc=dirk.behme@de.bosch.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.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.