From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Thomas Abraham <thomas.abraham@linaro.org>,
linux-kernel@vger.kernel.org, k.lewandowsk@samsung.com,
devicetree-discuss@lists.ozlabs.org, rob.herring@calxeda.com,
grant.likely@secretlab.ca, kgene.kim@samsung.com,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, patches@linaro.org
Subject: Re: [PATCH v4 1/2] mfd: add irq domain support for max8997 interrupts
Date: Mon, 16 Apr 2012 17:32:24 +0200 [thread overview]
Message-ID: <20120416153224.GF24130@sortiz-mobl> (raw)
In-Reply-To: <20120404212257.GE10787@opensource.wolfsonmicro.com>
Hi Mark,
On Wed, Apr 04, 2012 at 10:22:57PM +0100, Mark Brown wrote:
> On Sat, Mar 24, 2012 at 03:19:49PM +0530, Thomas Abraham wrote:
> > Add irq domain support for max8997 interrupts. The reverse mapping method
> > used is linear mapping since the sub-drivers of max8997 such as regulator
> > and charger drivers can use the max8997 irq_domain to get the linux irq
> > number for max8997 interrupts. All uses of irq_base in platform data and
> > max8997 driver private data are removed.
>
> > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> > Acked-by: Grant Likely <grant.likely@secretlab.ca>
>
> CCing in Samuel for the MFD review - review tends to be faster if you CC
> maintainers! Samuel, there's a followup patch for the regulator API
> which is likely to collide with some API updates so is it OK to merge
> via regulator if the patch is OK?
Yes, the patch looks fine, you can merge it through the regulator tree with my
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
if you think that's necessary.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] mfd: add irq domain support for max8997 interrupts
Date: Mon, 16 Apr 2012 17:32:24 +0200 [thread overview]
Message-ID: <20120416153224.GF24130@sortiz-mobl> (raw)
In-Reply-To: <20120404212257.GE10787@opensource.wolfsonmicro.com>
Hi Mark,
On Wed, Apr 04, 2012 at 10:22:57PM +0100, Mark Brown wrote:
> On Sat, Mar 24, 2012 at 03:19:49PM +0530, Thomas Abraham wrote:
> > Add irq domain support for max8997 interrupts. The reverse mapping method
> > used is linear mapping since the sub-drivers of max8997 such as regulator
> > and charger drivers can use the max8997 irq_domain to get the linux irq
> > number for max8997 interrupts. All uses of irq_base in platform data and
> > max8997 driver private data are removed.
>
> > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> > Acked-by: Grant Likely <grant.likely@secretlab.ca>
>
> CCing in Samuel for the MFD review - review tends to be faster if you CC
> maintainers! Samuel, there's a followup patch for the regulator API
> which is likely to collide with some API updates so is it OK to merge
> via regulator if the patch is OK?
Yes, the patch looks fine, you can merge it through the regulator tree with my
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
if you think that's necessary.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-04-16 15:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 9:49 [PATCH v4 0/2] regulator: add irq domain and device tree support for MAX8997 Thomas Abraham
2012-03-24 9:49 ` Thomas Abraham
2012-03-24 9:49 ` Thomas Abraham
2012-03-24 9:49 ` [PATCH v4 1/2] mfd: add irq domain support for max8997 interrupts Thomas Abraham
2012-03-24 9:49 ` Thomas Abraham
2012-03-24 9:49 ` Thomas Abraham
2012-03-26 12:20 ` MyungJoo Ham
2012-03-26 12:20 ` MyungJoo Ham
2012-03-30 22:06 ` Grant Likely
2012-03-30 22:06 ` Grant Likely
2012-04-17 18:11 ` Thomas Abraham
2012-04-17 18:11 ` Thomas Abraham
2012-04-04 21:22 ` Mark Brown
2012-04-04 21:22 ` Mark Brown
2012-04-16 15:32 ` Samuel Ortiz [this message]
2012-04-16 15:32 ` Samuel Ortiz
2012-04-16 18:47 ` Mark Brown
2012-04-16 18:47 ` Mark Brown
2012-03-24 9:49 ` [PATCH v4 2/2] regulator: add device tree support for max8997 Thomas Abraham
2012-03-24 9:49 ` Thomas Abraham
2012-03-27 6:40 ` MyungJoo Ham
2012-03-27 6:40 ` MyungJoo Ham
2012-03-28 17:03 ` Karol Lewandowski
2012-03-28 17:03 ` Karol Lewandowski
2012-04-17 18:35 ` Thomas Abraham
2012-04-17 18:35 ` Thomas Abraham
2012-04-17 18:38 ` Mark Brown
2012-04-17 18:38 ` Mark Brown
2012-04-18 8:16 ` Thomas Abraham
2012-04-18 8:16 ` Thomas Abraham
2012-03-30 22:09 ` Grant Likely
2012-03-30 22:09 ` Grant Likely
2012-04-16 18:51 ` Mark Brown
2012-04-16 18:51 ` Mark Brown
2012-04-16 18:56 ` Thomas Abraham
2012-04-16 18:56 ` Thomas Abraham
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=20120416153224.GF24130@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=k.lewandowsk@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=thomas.abraham@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.