Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: a0393675@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/5] mfd: tps65218: Clean ups
Date: Fri, 16 Sep 2016 21:51:38 +0530	[thread overview]
Message-ID: <0a30f210-0a23-0899-51b0-28f200ddd0a4@ti.com> (raw)
In-Reply-To: <20160916133153.GB27974@sirena.org.uk>



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
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.

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.

>
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, though there are some other maintainers who like them - if in
> doubt look at how patches for the subsystem are normally handled.
>

  reply	other threads:[~2016-09-16 16:21 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
2016-09-16 11:42 ` Keerthy
2016-09-16 13:31   ` Mark Brown
2016-09-16 16:21     ` Keerthy [this message]
2016-09-16 17:36       ` Mark Brown
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=0a30f210-0a23-0899-51b0-28f200ddd0a4@ti.com \
    --to=a0393675@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox