From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH RFT] regulator: Add support for tps62362 and tps62363 in tps62360-regulator driver
Date: Mon, 2 Apr 2012 23:16:21 +0100 [thread overview]
Message-ID: <20120402221620.GK3160@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1333361968.2802.1.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
On Mon, Apr 02, 2012 at 06:19:28PM +0800, Axel Lin wrote:
> According to the datasheet[1], tps62360 is register compatible with tps62362.
> tps62361B is register compatible with tps62363.
> Thus this patch adds support for tps62362 and tps62363.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-02 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 10:19 [PATCH RFT] regulator: Add support for tps62362 and tps62363 in tps62360-regulator driver Axel Lin
2012-04-02 10:20 ` Laxman Dewangan
2012-04-02 22:16 ` 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=20120402221620.GK3160@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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.