From: Matthias Brugger <matthias.bgg@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] dm: core: Walk the tree to find address- and size-cells properties
Date: Sat, 11 Apr 2020 20:05:11 +0200 [thread overview]
Message-ID: <81c54d79-c1ea-e8af-60f7-85d9fc2daff0@gmail.com> (raw)
In-Reply-To: <CAPnjgZ3kWdW-BDf2+Yo8fE6qOzK5bMmY74Ub=4g2O_6yb8Qgqg@mail.gmail.com>
Hi Simon,
On 4/9/20 6:25 PM, Simon Glass wrote:
> Hi Matthias,
>
> On Wed, 8 Apr 2020 at 03:35, <matthias.bgg@kernel.org> wrote:
>>
>> From: Matthias Brugger <mbrugger@suse.com>
>>
>> Walk the tree when reading size-cells or address-cells properties.
>>
>> Reported-by: Robin Randhawa <Robin.Randhawa@ARM.com>
>> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
>>
>> ---
>>
>> drivers/core/ofnode.c | 8 ++++----
>> include/dm/ofnode.h | 36 ++++++++++++++++++++++++++++++++++++
>> include/dm/read.h | 6 ++----
>> 3 files changed, 42 insertions(+), 8 deletions(-)
>>
>
> Please can you send these upstream? I think you'll need to add a test
> when doing that, too.
>
What is the upstream project for drivers/core/ofnode.c? I wasn't able to
find it.
Regards,
Matthias
next prev parent reply other threads:[~2020-04-11 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 9:35 [PATCH 0/2] Reading size-cells and address-cells from a node should walk up the matthias.bgg at kernel.org
2020-04-08 9:35 ` [PATCH 1/2] libfdt: Make fdt_cells function accessible matthias.bgg at kernel.org
2020-04-09 16:25 ` Simon Glass
2020-04-08 9:35 ` [PATCH 2/2] dm: core: Walk the tree to find address- and size-cells properties matthias.bgg at kernel.org
2020-04-09 16:25 ` Simon Glass
2020-04-11 18:05 ` Matthias Brugger [this message]
2020-04-19 23:37 ` Simon Glass
2020-04-08 14:48 ` [PATCH 0/2] Reading size-cells and address-cells from a node should walk up the Robin Randhawa
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=81c54d79-c1ea-e8af-60f7-85d9fc2daff0@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=u-boot@lists.denx.de \
/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