linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, lgirdwood@gmail.com,
	sameo@linux.intel.com, linux-kernel@vger.kernel.org,
	lee.jones@linaro.org
Subject: Re: [PATCH-v3] mfd: 88pm80x: Add 88pm860 chip type support
Date: Tue, 25 Aug 2015 14:02:07 +0530	[thread overview]
Message-ID: <55DC2807.5020202@linaro.org> (raw)
In-Reply-To: <20150825063825.GE27431@sirena.org.uk>



On Tuesday 25 August 2015 12:08 PM, Mark Brown wrote:
> On Mon, Aug 24, 2015 at 12:32:17PM +0530, Vaibhav Hiremath wrote:
>> On Monday 20 July 2015 05:22 PM, Vaibhav Hiremath wrote:
>>> Add chip identification support for 88PM860 device
>>> to the pm80x_chip_mapping table.
>
>> Last update/understanding which I have on this patch is,
>>
>> Lee is OK with taking this patch from regulator tree.
>> Lee please let me know if you think otherwise.
>>
>> With this patch in, the build dependency will go away.
>>
>> Request to pick this patch into your topic/88pm800 branch and run build
>> test.
>
> Please don't send content free pings, they just waste time.  I can't
> review or apply content free pings.  Please submit patches following the
> process in SubmittingPatches.
>
> The chances are I deleted this mail unread since it is a MFD patch...
>

Hmmm Ok,

Resending now...

Thanks,
Vaibhav

      reply	other threads:[~2015-08-25  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 11:52 [PATCH-v3] mfd: 88pm80x: Add 88pm860 chip type support Vaibhav Hiremath
2015-07-21 15:12 ` Lee Jones
2015-08-24  7:02 ` Vaibhav Hiremath
2015-08-25  6:38   ` Mark Brown
2015-08-25  8:32     ` Vaibhav Hiremath [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=55DC2807.5020202@linaro.org \
    --to=vaibhav.hiremath@linaro.org \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).