From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
swarren@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt
Date: Wed, 14 Nov 2012 10:24:41 +0900 [thread overview]
Message-ID: <20121114012439.GF4415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121113195637.GQ27828@sortiz-mobl>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Tue, Nov 13, 2012 at 08:56:37PM +0100, Samuel Ortiz wrote:
> The patchset looks fine, but it should either go through Mark's tree or I
> should merge Mark's regmap_irq_get_domain patch to my for-next branch.
> Mark, any preference ?
I don't mind that much, there's a tag in my regmap tree you can pull in
to integrate or I can apply things just as easily.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-14 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:03 [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 1/4] mfd: tps65910: Initialize mfd devices after all initialization done Laxman Dewangan
2012-11-13 14:03 ` [PATCH RESEND V3 2/4] mfd: tps65910: use regmap irq framework for interrupt support Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 3/4] mfd: tps65910: move interrupt implementation code to mfd file Laxman Dewangan
2012-11-13 14:03 ` [PATCH V3 RESEND 4/4] mfd: tps65910: pass irq_domain when adding mfd sub devices Laxman Dewangan
2012-11-13 19:56 ` [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt Samuel Ortiz
2012-11-14 1:24 ` Mark Brown [this message]
2012-11-18 23:23 ` Samuel Ortiz
2012-11-19 3:50 ` 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=20121114012439.GF4415@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--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 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.