From: ddaney.cavm@gmail.com
To: linux-mips@linux-mips.org, ralf@linux-mips.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org
Cc: David Daney <david.daney@cavium.com>
Subject: [PATCH 0/2] of: Allow scripts/dtc/libfdt to be used from kernel code and more...
Date: Thu, 10 Nov 2011 17:11:27 -0800 [thread overview]
Message-ID: <1320973889-30079-1-git-send-email-ddaney.cavm@gmail.com> (raw)
From: David Daney <david.daney@cavium.com>
My next patch set for OCTEON device tree support relies on these two
patches. I split these out as they are architecture independent.
I iterated on these several times under the guise of an RFC, this is
their first appearance as a request to be merged.
Thanks,
David Daney (2):
of/lib: Allow scripts/dtc/libfdt to be used from kernel code
of: Make of_find_node_by_path() traverse /aliases for relative paths.
drivers/of/base.c | 65 +++++++++++++++++++++++++++++++++++++++++--
include/linux/libfdt.h | 8 +++++
include/linux/libfdt_env.h | 13 +++++++++
lib/Kconfig | 6 ++++
lib/Makefile | 5 +++
lib/fdt.c | 2 +
lib/fdt_ro.c | 2 +
lib/fdt_rw.c | 2 +
lib/fdt_strerror.c | 2 +
lib/fdt_sw.c | 2 +
lib/fdt_wip.c | 2 +
11 files changed, 106 insertions(+), 3 deletions(-)
create mode 100644 include/linux/libfdt.h
create mode 100644 include/linux/libfdt_env.h
create mode 100644 lib/fdt.c
create mode 100644 lib/fdt_ro.c
create mode 100644 lib/fdt_rw.c
create mode 100644 lib/fdt_strerror.c
create mode 100644 lib/fdt_sw.c
create mode 100644 lib/fdt_wip.c
--
1.7.2.3
next reply other threads:[~2011-11-11 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 1:11 ddaney.cavm [this message]
2011-11-11 1:11 ` [PATCH 1/2] of/lib: Allow scripts/dtc/libfdt to be used from kernel code ddaney.cavm
2011-11-11 1:11 ` [PATCH 2/2] of: Make of_find_node_by_path() traverse /aliases for relative paths ddaney.cavm
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=1320973889-30079-1-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=david.daney@cavium.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®