From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
David Dajun Chen <dchen@diasemi.com>,
Ashish Jangam <ashish.jangam@kpitcummins.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH RFC/RFT 1/2] regulator: Fix da9052 ldo regulator names
Date: Thu, 15 Mar 2012 10:49:31 +0000 [thread overview]
Message-ID: <20120315104930.GE3138@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAF+7xWnNjJbdG2G8RBG_n5KdzCLXNe0RpJ2F99gFoP+R+AMYDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Thu, Mar 15, 2012 at 07:42:53AM +0800, Axel Lin wrote:
> commit 4adf9beda5 regulator: Fix mask parameter in da9052_reg_update calls
> commit 7b95765 regulator: Set n_voltages for da9052 regulators
> commit 93651218 regulator: da9052: Ensure the selected voltage falls
> within the specified range
> I'm not sure if I should re-generate these 2 patches against
> topic/drivers branch because
> you will have conflict when merge them to for-next branch then.
Those are bug fixes which are going to Linus, I guess I can merge them
over though as there's a direct conflict. Can you please resend the
patches as they were, I deleted them when they didn't apply?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-15 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 23:42 [PATCH RFC/RFT 1/2] regulator: Fix da9052 ldo regulator names Axel Lin
2012-03-06 23:46 ` [PATCH RFC/RFT 2/2] regulator: Refactor to use one da9052_ldo_ops/da9052_dcdc_ops for all LDOs/DCDCs Axel Lin
2012-03-14 14:09 ` [PATCH RFC/RFT 1/2] regulator: Fix da9052 ldo regulator names Mark Brown
2012-03-14 23:42 ` Axel Lin
2012-03-15 10:49 ` 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=20120315104930.GE3138@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ashish.jangam@kpitcummins.com \
--cc=axel.lin@gmail.com \
--cc=dchen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paul.liu@linaro.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 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.