From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, lee.jones@linaro.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [RESEND][PATCH V2 4/4] regulator: Add ROHM BD9571MWV-M PMIC regulator driver
Date: Wed, 26 Apr 2017 01:49:20 +0200 [thread overview]
Message-ID: <e694bd6d-0b7f-c30a-9db0-12d8a8cc2648@gmail.com> (raw)
In-Reply-To: <20170425223106.zriauibqrboxaj4b@sirena.org.uk>
On 04/26/2017 12:31 AM, Mark Brown wrote:
> On Tue, Apr 25, 2017 at 08:32:10PM +0200, Marek Vasut wrote:
>> Add driver for the regulator block in the ROHM BD9571MWV-W MFD PMIC.
>> This block supports three voltage monitors, VD18, VD25, VD33 for the
>> 1V8, 2V5, 3V3 voltage rails and a single voltage regulator for the
>> DVFS rail.
>
> Please do not submit new versions of already applied patches, please
> submit incremental updates to the existing code. Modifying existing
> commits creates problems for other users building on top of those
> commits so it's best practice to only change pubished git commits if
> absolutely essential.
I resubmitted this on Lee's request [1].
[1]
https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg13599.html
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-04-25 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170425183210.30594-1-marek.vasut+renesas@gmail.com>
2017-04-25 18:32 ` [RESEND][PATCH V2 2/4] mfd: Add ROHM BD9571MWV-M MFD PMIC driver Marek Vasut
2017-04-25 18:32 ` [RESEND][PATCH V2 4/4] regulator: Add ROHM BD9571MWV-M PMIC regulator driver Marek Vasut
2017-04-25 22:31 ` Mark Brown
2017-04-25 23:49 ` Marek Vasut [this message]
2017-04-26 8:43 ` Lee Jones
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=e694bd6d-0b7f-c30a-9db0-12d8a8cc2648@gmail.com \
--to=marek.vasut@gmail.com \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.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
Powered by JetHome