From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
lgirdwood@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/4] regulator: core: Add support for active-discharge configuration
Date: Wed, 2 Mar 2016 16:21:32 +0530 [thread overview]
Message-ID: <56D6C5B4.3050608@nvidia.com> (raw)
In-Reply-To: <20160302102521.GE18327@sirena.org.uk>
On Wednesday 02 March 2016 03:55 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 02, 2016 at 12:32:10PM +0530, Laxman Dewangan wrote:
>> Add support to enable/disable active discharge of regulator via
>> machine constraints. This configuration is done when setting
>> machine constraint during regulator register and if regulator
>> driver implemented the callback ops.
> I'm missing patches 1, 3 and 4 here. Please don't send patches numbered
> as part of a series outside of the series, it makes things confusing.
>
> * Unknown Key
> * 0x5D5487D0
I sent full series of V2 but unfortunately (which I missed), 2/4 did not
have V2 in its subject and resend again on 2/4 with V2 in its subject.
Let me resend all patches again.
Sorry for inconvenience created.
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <lgirdwood@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 2/4] regulator: core: Add support for active-discharge configuration
Date: Wed, 2 Mar 2016 16:21:32 +0530 [thread overview]
Message-ID: <56D6C5B4.3050608@nvidia.com> (raw)
In-Reply-To: <20160302102521.GE18327@sirena.org.uk>
On Wednesday 02 March 2016 03:55 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 02, 2016 at 12:32:10PM +0530, Laxman Dewangan wrote:
>> Add support to enable/disable active discharge of regulator via
>> machine constraints. This configuration is done when setting
>> machine constraint during regulator register and if regulator
>> driver implemented the callback ops.
> I'm missing patches 1, 3 and 4 here. Please don't send patches numbered
> as part of a series outside of the series, it makes things confusing.
>
> * Unknown Key
> * 0x5D5487D0
I sent full series of V2 but unfortunately (which I missed), 2/4 did not
have V2 in its subject and resend again on 2/4 with V2 in its subject.
Let me resend all patches again.
Sorry for inconvenience created.
next prev parent reply other threads:[~2016-03-02 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 7:02 [PATCH V2 2/4] regulator: core: Add support for active-discharge configuration Laxman Dewangan
2016-03-02 7:02 ` Laxman Dewangan
[not found] ` <1456902130-22406-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-02 10:25 ` Mark Brown
2016-03-02 10:25 ` Mark Brown
2016-03-02 10:51 ` Laxman Dewangan [this message]
2016-03-02 10:51 ` Laxman Dewangan
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=56D6C5B4.3050608@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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.