From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: ucb1x00: remove NO_IRQ check
Date: Wed, 7 Sep 2016 17:07:33 +0100 [thread overview]
Message-ID: <20160907160733.GO1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160907150846.GA4921@dell>
On Wed, Sep 07, 2016 at 04:08:46PM +0100, Lee Jones wrote:
> On Wed, 07 Sep 2016, Russell King - ARM Linux wrote:
> > It got sent for REVIEW COMMENTS and TESTING for people like Robert
> > Jarzmik and Adam, to get some sense as to the _entire_ series
> > acceptability to people. This is a _massive_ series, and it's still
> > growing. The series is now at more than 100 patches.
>
> We've already covered the fact that you should have sent it as an
> [RFC]. None of this would have happened if you'd done so. Let's
> leave it at that.
I wonder if you realise, or even known, given your relative inexperience,
that many people actually _ignore_ patches with a RFC tag, and provide
no review or comments against them. Remember, by your own admission,
there's twenty years experience difference between us.
I'm going to take one last issue with your comments:
> That's the problem, it was not clear, at all. You said you "could
> have arguably applied it earlier in the set". But without knowing
> that this wasn't a stand-alone set (how could I, you didn't mention
> that), what does the really mean?
So by your own admission, you weren't sure of the understanding, and
from the extract of your mailbox that you kindly provided earlier in
your reply:
> 30 2016 Russell King - AR ( 0) [PATCH 0/8] SA11x0/PXA remainder & cleanups
> 30 2016 Russell King ( 0) └>[PATCH 1/8] mfd: ucb1x00: allow IRQ probing to work with IRQs > 32
if that's all you saw, "earlier in the set" in the first message
wouldn't make any sense, and should've set alarm bells ringing that
something had gone wrong, or you were without complete information.
The reasonable thing to have done - especially by your own admission
that you found it confusing - would have been to ask for clarification.
You did not, you chose after just one hour (again, your admission) to
apply the patch.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-09-07 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 13:03 [PATCH] mfd: ucb1x00: remove NO_IRQ check Arnd Bergmann
2016-09-06 13:17 ` Russell King - ARM Linux
2016-09-06 13:49 ` Arnd Bergmann
2016-09-06 15:45 ` Lee Jones
2016-09-06 16:28 ` Russell King - ARM Linux
2016-09-07 10:27 ` Lee Jones
2016-09-07 11:27 ` Russell King - ARM Linux
2016-09-07 12:48 ` Lee Jones
2016-09-07 13:44 ` Russell King - ARM Linux
2016-09-07 15:08 ` Lee Jones
2016-09-07 16:07 ` Russell King - ARM Linux [this message]
2016-09-07 16:27 ` Lee Jones
2016-09-07 16:36 ` Russell King - ARM Linux
[not found] ` <1473265954.29864.15.camel@perches.com>
[not found] ` <20160907163854.GE4921@dell>
2016-09-07 19:47 ` rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP PATCH] Joe Perches
2016-09-07 21:49 ` Randy Dunlap
2016-09-14 19:03 ` Jonathan Corbet
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=20160907160733.GO1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=egtvedt@samfundet.no \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).