From: Stephen Warren <swarren@wwwdotorg.org>
To: Keerthy <j-keerthy@ti.com>
Cc: linux-omap@vger.kernel.org, broonie@kernel.org,
ldewangan@nvidia.com, sameo@linux.intel.com,
grant.likely@secretlab.ca, swarren@nvidia.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, gg@slimlogic.co.uk
Subject: Re: [PATCH v3 1/4] MFD: Palmas: Check if irq is valid
Date: Wed, 19 Jun 2013 11:08:53 -0600 [thread overview]
Message-ID: <51C1E5A5.9090105@wwwdotorg.org> (raw)
In-Reply-To: <1371621470-22279-2-git-send-email-j-keerthy@ti.com>
On 06/18/2013 11:57 PM, Keerthy wrote:
> From: J Keerthy <j-keerthy@ti.com>
>
> Check if irq value obtained is valid. If it is not valid
> then skip the irq request step and go ahead with the probe.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-06-19 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 5:57 [PATCH v3 0/4] MFD: Palmas: Add TPS659038 PMIC support on Palmas Keerthy
2013-06-19 5:57 ` [PATCH v3 1/4] MFD: Palmas: Check if irq is valid Keerthy
2013-06-19 16:42 ` Mark Brown
2013-06-20 4:16 ` J, KEERTHY
2013-06-19 17:08 ` Stephen Warren [this message]
2013-06-20 4:19 ` J, KEERTHY
2013-06-20 4:25 ` J, KEERTHY
2013-07-11 11:25 ` Lee Jones
2013-07-11 11:27 ` Lee Jones
2013-06-19 5:57 ` [PATCH v3 2/4] MFD: Palmas: Add SMPS10_BOOST feature Keerthy
2013-06-20 4:34 ` J, KEERTHY
2013-06-20 9:07 ` Samuel Ortiz
2013-06-20 9:13 ` J, KEERTHY
2013-06-20 9:27 ` Samuel Ortiz
2013-06-20 9:28 ` J, KEERTHY
2013-06-19 5:57 ` [PATCH v3 3/4] mfd: Palmas: Add TPS659038 PMIC support Keerthy
2013-06-20 8:41 ` Samuel Ortiz
2013-06-19 5:57 ` [PATCH v3 4/4] regulator: Palmas: Add TPS659038 support Keerthy
2013-06-19 16:42 ` Mark Brown
2013-06-20 4:19 ` J, KEERTHY
2013-06-20 8:39 ` [PATCH v3 0/4] MFD: Palmas: Add TPS659038 PMIC support on Palmas Samuel Ortiz
2013-06-20 8:41 ` J, KEERTHY
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=51C1E5A5.9090105@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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