From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Ying-Chun Liu (PaulLiu)" <paulliu@debian.org>
Cc: linux-kernel@vger.kernel.org, patches@linaro.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] regulator: da9052: fix bug in device tree iteration loop
Date: Mon, 7 May 2012 12:52:07 +0100 [thread overview]
Message-ID: <20120507115207.GA17002@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336377443-5926-1-git-send-email-paulliu@debian.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
On Mon, May 07, 2012 at 03:57:23PM +0800, Ying-Chun Liu (PaulLiu) wrote:
> From: "Ying-Chun Liu (PaulLiu)" <paulliu@debian.org>
>
> The driver of da9052 is buggy due to the iteration loop of device tree.
> This patch fix the loop condition to make the driver work with device tree.
Applied, thanks. I am wondering how this code was ever tested...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-07 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 7:57 [PATCH] regulator: da9052: fix bug in device tree iteration loop Ying-Chun Liu (PaulLiu)
2012-05-07 11:52 ` Mark Brown [this message]
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=20120507115207.GA17002@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=patches@linaro.org \
--cc=paulliu@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox