From: Samuel Ortiz <sameo@linux.intel.com>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mfd: tps65910-irq: Add devicetree init support
Date: Fri, 18 May 2012 11:53:45 +0200 [thread overview]
Message-ID: <20120518095345.GE12015@sortiz-mobl> (raw)
In-Reply-To: <1337036142-10899-1-git-send-email-rklein@nvidia.com>
Hi Rhyland,
On Mon, May 14, 2012 at 06:55:42PM -0400, Rhyland Klein wrote:
> This change changes the tps65910-irq code to use irqdomain, and support
> initialization from devicetree. This assumes that the irq_base in the platform
> data is -1 if devicetree is used.
>
> Signed-off-by: Rhyland Klein <rklein@nvidia.com>
Patch applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-05-18 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 22:55 [PATCH v4] mfd: tps65910-irq: Add devicetree init support Rhyland Klein
2012-05-18 9:53 ` Samuel Ortiz [this message]
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=20120518095345.GE12015@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rklein@nvidia.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