From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
Grant Likely <grant.likely@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] mfd: Add device tree bindings for Arizona class devices
Date: Mon, 8 Apr 2013 16:30:08 +0200 [thread overview]
Message-ID: <20130408143008.GA21256@zurbaran> (raw)
In-Reply-To: <1364938728-7732-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Tue, Apr 02, 2013 at 10:38:48PM +0100, Mark Brown wrote:
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> Documentation/devicetree/bindings/mfd/arizona.txt | 62 ++++++++++++++++++++
> drivers/mfd/arizona-core.c | 64 +++++++++++++++++++++
> drivers/mfd/arizona-i2c.c | 10 +++-
> drivers/mfd/arizona-spi.c | 10 +++-
> drivers/mfd/arizona.h | 12 ++++
> 5 files changed, 154 insertions(+), 4 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mfd/arizona.txt
This is the one that caused the build failure around missing
arizona_of_get_core_pdata() with !CONFIG_OF, so I'm leaving this one out for
now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-04-08 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:38 [PATCH] mfd: Add device tree bindings for Arizona class devices Mark Brown
2013-04-08 9:27 ` Samuel Ortiz
2013-04-08 14:30 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-02 20:51 Mark Brown
2013-04-02 21:38 ` Mark Brown
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=20130408143008.GA21256@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/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).