devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Keerthy <a0393675@ti.com>
Cc: Keerthy <j-keerthy@ti.com>,
	lee.jones@linaro.org, tony@atomide.com,
	dmitry.torokhov@gmail.com, linus.walleij@linaro.org,
	gnurou@gmail.com, devicetree@vger.kernel.org, robh+dt@kernel.org,
	linux-input@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, t-kristo@ti.com,
	russ.dill@ti.com, d-gerlach@ti.com, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/5] mfd: tps65218: Clean ups
Date: Fri, 16 Sep 2016 18:36:20 +0100	[thread overview]
Message-ID: <20160916173620.GB10189@sirena.org.uk> (raw)
In-Reply-To: <0a30f210-0a23-0899-51b0-28f200ddd0a4@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Fri, Sep 16, 2016 at 09:51:38PM +0530, Keerthy wrote:
> On Friday 16 September 2016 07:01 PM, Mark Brown wrote:
> > On Fri, Sep 16, 2016 at 05:12:38PM +0530, Keerthy wrote:

> > > Should i repost this series? I do not see this series in linux-next yet.

> > Please don't send content free pings and please allow a reasonable time
> > for review.  People get busy, go on holiday, attend conferences and so

> I should have been clearer.
> The last Lee Jones conveyed that:

> "I can't take this series yet, since it relies on a change which was
> taken into Mark's Regulator tree"

> https://lkml.org/lkml/2016/8/31/312

> So wanted to check if i needed to re-base/repost this series again.
> Sorry about the confusion i think that is because of $Subject goof up in the
> 0th patch of the series.

I'm afraid I've no real idea what this series is about or what patches
it might depend on, sorry.  If you're waiting for me to do something
you'll need to tell me what it is but if it's a dependency that needs
cross merging then reposting this series isn't going to be needed.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-09-16 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 12:54 [PATCH v7 0/5] mfd: tps65218: Clean ups Keerthy
     [not found] ` <1470833641-29546-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-09-16 11:42   ` Keerthy
     [not found]     ` <ab94aff0-8470-57e5-2039-12f09bb0ca33-l0cyMroinI0@public.gmane.org>
2016-09-16 13:31       ` Mark Brown
     [not found]         ` <20160916133153.GB27974-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-09-16 16:21           ` Keerthy
2016-09-16 17:36             ` Mark Brown [this message]
2016-09-17  3:53               ` Keerthy

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=20160916173620.GB10189@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=a0393675@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=j-keerthy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=russ.dill@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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).