From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: gregkh@linuxfoundation.org, sameo@linux.intel.com,
swarren@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 4/5] regmap: add API to get irq_domain from regmap irq
Date: Mon, 15 Oct 2012 09:56:36 +0900 [thread overview]
Message-ID: <20121015005634.GA24935@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1349889545-21517-5-git-send-email-ldewangan@nvidia.com>
On Wed, Oct 10, 2012 at 10:49:04PM +0530, Laxman Dewangan wrote:
> Add API regmap_irq_get_irq_domain() for getting the
> irq domain from regmap irq. The irq domain created on
> result of regmap_add_irq_chip() from driver.
Sorry, when doing the merge down after the merge window I realised that
I already have a patch there adding a function regmap_irq_get_domain()
which has been sitting there for a while now, I think it was just fat
fingers that meant it didn't make v3.7.
next prev parent reply other threads:[~2012-10-15 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 17:19 [PATCH V2 0/5]mfd: tps65910: use regmap irq framework for interrupt Laxman Dewangan
2012-10-10 17:19 ` [PATCH V2 1/5] mfd: tps65910: Initialize mfd devices after all initialization done Laxman Dewangan
2012-10-10 17:19 ` [PATCH V2 2/5] mfd: tps65910: use regmap irq framework for interrupt support Laxman Dewangan
2012-10-10 17:19 ` [PATCH V2 3/5] mfd: tps65910: move interrupt implementation code to mfd file Laxman Dewangan
2012-10-10 17:19 ` [PATCH V2 4/5] regmap: add API to get irq_domain from regmap irq Laxman Dewangan
2012-10-11 7:38 ` Mark Brown
2012-10-15 0:56 ` Mark Brown [this message]
2012-10-15 11:41 ` Laxman Dewangan
2012-10-10 17:19 ` [PATCH V2 5/5] mfd: tps65910: pass irq_domain when adding mfd sub devices Laxman Dewangan
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=20121015005634.GA24935@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=swarren@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