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 3/5] mfd: tps65910: Initialize mfd devices after all initialization done
Date: Wed, 10 Oct 2012 12:09:07 +0900 [thread overview]
Message-ID: <20121010030906.GG17288@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1349782116-9757-4-git-send-email-ldewangan@nvidia.com>
On Tue, Oct 09, 2012 at 04:58:34PM +0530, Laxman Dewangan wrote:
> Add sub devices of tps65910 after all initialization like interrupt,
> clock etc. is done. This will make sure that require data gets
> initialized properly before sub devices probe's get called.
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
but isn't this needed as a bug fix and so shouldn't it be the first
patch in the series and go in for v3.7?
next prev parent reply other threads:[~2012-10-10 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 11:28 [PATCH 0/5] mfd: tps65910: use regmap irq framework for interrupt Laxman Dewangan
2012-10-09 11:28 ` [PATCH 1/5] mfd: tps65910: use regmap irq framework for interrupt support Laxman Dewangan
2012-10-10 3:07 ` Mark Brown
2012-10-09 11:28 ` [PATCH 2/5] mfd: tps65910: move interrupt implementation code to mfd file Laxman Dewangan
2012-10-10 3:08 ` Mark Brown
2012-10-09 11:28 ` [PATCH 3/5] mfd: tps65910: Initialize mfd devices after all initialization done Laxman Dewangan
2012-10-10 3:09 ` Mark Brown [this message]
2012-10-09 11:28 ` [PATCH 4/5] regmap: add API to get irq_domain from regmap irq Laxman Dewangan
2012-10-10 2:08 ` Mark Brown
2012-10-09 11:28 ` [PATCH 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=20121010030906.GG17288@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 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.