qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eric Auger <eric.auger.pro@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] ARM virt: Silence dtc warnings
Date: Tue, 26 Jun 2018 19:15:05 +0200	[thread overview]
Message-ID: <a49d3e03-a6aa-b627-c2e3-2b3c4bddf74d@redhat.com> (raw)
In-Reply-To: <CAFEAcA9Pg3C+XD7WuLyNr5RfifRCvXB6t01YuLiK9Cs15v-Dpg@mail.gmail.com>

Hi Peter,

On 06/26/2018 07:06 PM, Peter Maydell wrote:
> On 22 June 2018 at 14:22, Eric Auger <eric.auger@redhat.com> wrote:
>> When running dtc on the guest /proc/device-tree, we get the
>> following warnings: "Warning (unit_address_vs_reg): Node <name>
>> has a reg or ranges property, but no unit name", with name:
>> /intc, /intc/its, /intc/v2m, /memory.
>>
>> This series removes those warnings by adding the unit address to
>> the corresponding node names.
> 
> This didn't apply to my target-arm.next tree. Once I've
> applied my on-list arm pullreq to master, could you
> rebase it, please?

Sure

Thanks

Eric
> 
> thanks
> -- PMM
> 

  reply	other threads:[~2018-06-26 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 13:22 [Qemu-devel] [PATCH v3 0/3] ARM virt: Silence dtc warnings Eric Auger
2018-06-22 13:22 ` [Qemu-devel] [PATCH v3 1/3] device_tree: Add qemu_fdt_node_unit_path Eric Auger
2018-06-22 13:22 ` [Qemu-devel] [PATCH v3 2/3] hw/arm/virt: Silence dtc /intc warnings Eric Auger
2018-06-22 13:22 ` [Qemu-devel] [PATCH v3 3/3] hw/arm/virt: Silence dtc /memory warning Eric Auger
2018-06-26 17:06 ` [Qemu-devel] [PATCH v3 0/3] ARM virt: Silence dtc warnings Peter Maydell
2018-06-26 17:15   ` Auger Eric [this message]
2018-06-26 18:18     ` Peter Maydell

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=a49d3e03-a6aa-b627-c2e3-2b3c4bddf74d@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=agraf@suse.de \
    --cc=crosthwaite.peter@gmail.com \
    --cc=eric.auger.pro@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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).