From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/3] of: make of_mutex public
Date: Tue, 30 Jun 2015 23:44:09 +0200 [thread overview]
Message-ID: <1435700651-3543-2-git-send-email-wsa@the-dreams.de> (raw)
In-Reply-To: <1435700651-3543-1-git-send-email-wsa@the-dreams.de>
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
If we want to use OF_DYNAMIC features outside the of framework, we need
to access this lock. If OF maintainers don't like exporting, we can
maybe create accessor functions that we can use?
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
drivers/of/of_private.h | 1 -
include/linux/of.h | 2 ++
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/of/of_private.h b/drivers/of/of_private.h
index 8e882e706cd8c6..f92ec41efb5dfd 100644
--- a/drivers/of/of_private.h
+++ b/drivers/of/of_private.h
@@ -31,7 +31,6 @@ struct alias_prop {
char stem[0];
};
-extern struct mutex of_mutex;
extern struct list_head aliases_lookup;
extern struct kset *of_kset;
diff --git a/include/linux/of.h b/include/linux/of.h
index b871ff9d81d720..f0464efcbdc5aa 100644
--- a/include/linux/of.h
+++ b/include/linux/of.h
@@ -32,6 +32,8 @@
typedef u32 phandle;
typedef u32 ihandle;
+extern struct mutex of_mutex;
+
struct property {
char *name;
int length;
--
2.1.4
next prev parent reply other threads:[~2015-06-30 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:44 [RFC 0/3] switch I2C IP cores at runtime Wolfram Sang
2015-06-30 21:44 ` Wolfram Sang [this message]
2015-07-03 4:43 ` [RFC 1/3] of: make of_mutex public Rob Herring
2015-07-03 6:54 ` Pantelis Antoniou
2015-07-03 7:24 ` Wolfram Sang
2015-06-30 21:44 ` [RFC 2/3] i2c: mux: demux-pinctrl: add driver Wolfram Sang
2015-07-01 7:08 ` Geert Uytterhoeven
2015-07-01 10:07 ` Wolfram Sang
2015-06-30 21:44 ` [RFC 3/3] ARM: shmobile: r8a7790: rework dts to use i2c demuxer Wolfram Sang
2015-07-01 7:10 ` Geert Uytterhoeven
2015-07-01 10:08 ` Wolfram Sang
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=1435700651-3543-2-git-send-email-wsa@the-dreams.de \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).