From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, Gary King <gking@nvidia.com>
Subject: Re: [PATCH] regulator: tps6586x: fix millivolt return values and SM2 table
Date: Fri, 30 Jul 2010 13:20:18 -0700 [thread overview]
Message-ID: <20100730202017.GA29726@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1280519938-3089-1-git-send-email-mike@compulab.co.il>
On Fri, Jul 30, 2010 at 10:58:58PM +0300, Mike Rapoport wrote:
> From: Gary King <gking@nvidia.com>
>
> Hi Liam,
> Below are bugfixes for the tps6586x spotted by Gary King.
> Please add this patch to your regulator tree.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-07-30 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 19:58 [PATCH] regulator: tps6586x: fix millivolt return values and SM2 table Mike Rapoport
2010-07-30 20:20 ` Mark Brown [this message]
2010-08-02 10:09 ` Liam Girdwood
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=20100730202017.GA29726@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gking@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mike@compulab.co.il \
/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