From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC GIT PULL, v2] RCU changes for v4.12
Date: Thu, 11 May 2017 08:54:50 +0200 [thread overview]
Message-ID: <20170511065449.o4ujfelu7uuoaxic@gmail.com> (raw)
In-Reply-To: <CA+55aFxzKqvkdCvd00MZBA+svpNzjHXggFYNvfcanaKbVoseJA@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, May 10, 2017 at 12:54 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Yeah, you are right and sorry about that - I have removed the patch
> > generation from my pull request scripts, so it shouldn't happen in
> > the future.
>
> I do have to say, that during the later -rc series in particular when
> people send me smaller fixes, I enjoy seeing the full patches.
I find them useful too, and to answer your original question:
> > Nobody is ever going to review a 300kB patch that is ~7500 lines.
I _did_ skim over that 300K patch, because I always try to do a final manual check
on the raw diffs I'm sending to you, and also to make it very clear what was sent
from a full disclosure and security log POV, independent of the Git pull space.
When patches are way too long, for example as the perf pull request diffs often
are, I trim them, so it's never an absolute, script-only thing.
Still it's not an excuse:
- I doubt anyone else but me would skim over a 30K (let alone a 300K) patch,
- I also missed the pain large patches cause in Gmail replies (with Mutt that
pain is considerably less),
- plus, most importantly, I didn't notice that the extra RCU mode bloat was one
too many in an already sizable line-up of RCU complexity ...
Thanks,
Ingo
next prev parent reply other threads:[~2017-05-11 6:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 9:59 [GIT PULL] " Ingo Molnar
2017-05-02 1:19 ` Linus Torvalds
2017-05-02 4:02 ` Paul E. McKenney
2017-05-02 4:11 ` Linus Torvalds
2017-05-02 4:30 ` Paul E. McKenney
2017-05-02 7:59 ` Ingo Molnar
2017-05-02 8:31 ` [PATCH] srcu: Debloat the <linux/rcu_segcblist.h> header Ingo Molnar
2017-05-02 10:25 ` Paul E. McKenney
2017-05-02 12:56 ` Paul E. McKenney
2017-05-09 7:26 ` [RFC GIT PULL, v2] RCU changes for v4.12 Ingo Molnar
2017-05-10 17:27 ` Linus Torvalds
2017-05-10 19:54 ` Ingo Molnar
2017-05-10 20:01 ` Linus Torvalds
2017-05-11 6:54 ` Ingo Molnar [this message]
2017-05-10 19:54 ` Paul E. McKenney
2017-05-10 20:17 ` Linus Torvalds
2017-05-10 20:51 ` Paul E. McKenney
2017-05-10 21:08 ` Linus Torvalds
2017-05-10 22:53 ` Paul E. McKenney
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=20170511065449.o4ujfelu7uuoaxic@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome