From: keerthy <j-keerthy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lee.jones@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <t-kristo@ti.com>
Subject: Re: [RESEND PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support
Date: Thu, 13 Jun 2019 23:39:55 +0530 [thread overview]
Message-ID: <7b500f5d-9ea0-0135-7174-b7a34db23d28@ti.com> (raw)
In-Reply-To: <20190613173248.GP5316@sirena.org.uk>
On 6/13/2019 11:02 PM, Mark Brown wrote:
> On Thu, Jun 13, 2019 at 10:32:45PM +0530, keerthy wrote:
>> On 6/13/2019 9:15 PM, Mark Brown wrote:
>>> On Wed, Jun 12, 2019 at 08:16:20PM +0530, Keerthy wrote:
>
>>>> patches 1/3 2/3 are already applied to linux-next.
>
>>> This doesn't build without those patches:
>
>> They are already on next. Do you want me to resend them as well?
>
> That's no good, it still breaks the build of my tree. I can't apply
> this until the code is in my tree, either through a shared branch or
> through Lihus' tree. I see I acked the patch, I'll have been expecting
> the patch to be applied to Lee's tree. If that's not possible or
> there's no branch then please resend after the merge window.
Lee Jones,
Could you please pull this patch?
- Keerthy
>
WARNING: multiple messages have this Message-ID (diff)
From: keerthy <j-keerthy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, t-kristo@ti.com
Subject: Re: [RESEND PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support
Date: Thu, 13 Jun 2019 23:39:55 +0530 [thread overview]
Message-ID: <7b500f5d-9ea0-0135-7174-b7a34db23d28@ti.com> (raw)
In-Reply-To: <20190613173248.GP5316@sirena.org.uk>
On 6/13/2019 11:02 PM, Mark Brown wrote:
> On Thu, Jun 13, 2019 at 10:32:45PM +0530, keerthy wrote:
>> On 6/13/2019 9:15 PM, Mark Brown wrote:
>>> On Wed, Jun 12, 2019 at 08:16:20PM +0530, Keerthy wrote:
>
>>>> patches 1/3 2/3 are already applied to linux-next.
>
>>> This doesn't build without those patches:
>
>> They are already on next. Do you want me to resend them as well?
>
> That's no good, it still breaks the build of my tree. I can't apply
> this until the code is in my tree, either through a shared branch or
> through Lihus' tree. I see I acked the patch, I'll have been expecting
> the patch to be applied to Lee's tree. If that's not possible or
> there's no branch then please resend after the merge window.
Lee Jones,
Could you please pull this patch?
- Keerthy
>
next prev parent reply other threads:[~2019-06-13 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 14:46 [RESEND PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support Keerthy
2019-06-12 14:46 ` Keerthy
2019-06-13 15:45 ` Mark Brown
2019-06-13 17:02 ` keerthy
2019-06-13 17:02 ` keerthy
2019-06-13 17:32 ` Mark Brown
2019-06-13 18:09 ` keerthy [this message]
2019-06-13 18:09 ` keerthy
2019-06-17 7:03 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v5.3 merge window Lee Jones
2019-06-17 7:15 ` Keerthy
2019-06-17 7:15 ` Keerthy
2019-07-02 10:46 ` [GIT PULL v2] " 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=7b500f5d-9ea0-0135-7174-b7a34db23d28@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@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.