From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linaro-kernel@lists.linaro.org, Mark Brown <broonie@kernel.org>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily
Date: Wed, 5 Oct 2016 14:25:36 +0530 [thread overview]
Message-ID: <20161005085536.GC31416@vireshk-i7> (raw)
In-Reply-To: <20161005084911.GG29257@dell>
On 05-10-16, 09:49, Lee Jones wrote:
> You are experienced enough to know better than this.
:)
> a) Contentless pings have never been acceptable. If you genuinely
> think a patch has been forgotten you should resubmit with a
> [RESEND]. That is their entire purpose.
Sure, but I really believe a light *ping* is much better than a complete resend
to start with. It generates far less noise.
> b) You submitted this patch right at the end of the release cycle, and
> your ping was sent during the merge-window. Most Maintainers, myself
> included, like to have patches soak tested in -next for at least a
> couple of weeks prior to acceptance.
I agree to that, I sent it after rc6. I wasn't looking to get this merged during
this cycle, but was wondering if it got missed or something like that.
I still don't think that a simple Ping was that bad of an option, but its fine.
Take your time to review this, no issues.
Cheers.
--
viresh
next prev parent reply other threads:[~2016-10-05 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 3:26 [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily Viresh Kumar
2016-09-16 3:26 ` [PATCH V2 2/3] mfd: wm8994-core: disable regulators before removing them Viresh Kumar
2016-10-26 12:22 ` Lee Jones
2016-09-16 3:27 ` [PATCH V2 3/3] mfd: wm8994-core: Don't use managed regulator bulk get API Viresh Kumar
2016-09-16 7:38 ` Charles Keepax
2016-10-26 12:22 ` Lee Jones
2016-10-26 12:24 ` Lee Jones
2016-09-16 7:37 ` [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily Charles Keepax
2016-10-03 10:56 ` Viresh Kumar
2016-10-04 14:41 ` Lee Jones
2016-10-05 0:39 ` Viresh Kumar
2016-10-05 8:49 ` Lee Jones
2016-10-05 8:55 ` Viresh Kumar [this message]
2016-10-05 9:10 ` Lee Jones
2016-10-26 12:20 ` 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=20161005085536.GC31416@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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