From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, akpm@linux-foundation.org,
davem@davemloft.net, dada1@cosmosbay.com, zbr@ioremap.net,
jeff.chua.linux@gmail.com, paulus@samba.org,
laijs@cn.fujitsu.com, jengelh@medozas.de, r000n@r000n.net,
benh@kernel.crashing.org, mathieu.desnoyers@polymtl.ca
Subject: Re: [PATCH -tip 0/3] expedited "big hammer" RCU grace periods
Date: Thu, 25 Jun 2009 09:47:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906250944511.3605@localhost.localdomain> (raw)
In-Reply-To: <20090625095953.GC29980@elte.hu>
On Thu, 25 Jun 2009, Ingo Molnar wrote:
>
> Our general preference is to zap code.
>
> /me stares at:
>
> $ git diff --stat -M v2.6.30..v2.6.31-rc1 | tail -1
> 7743 files changed, 782278 insertions(+), 403162 deletions(-)
>
> /me corrects himself:
Yes. Our general preference is to zap code, if only because it's so damn
unusual.
When one out of a hundred patches actually has more removals than
additions, we make a big deal out of it ("Look - I actually simplified
things"). For the 99 other patches we never size in polite company.
Oh well. But every time we add lines, we do it with the _best_ intentions.
Linus
next prev parent reply other threads:[~2009-06-25 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 16:45 Paul E. McKenney
2009-06-24 16:46 ` [PATCH -tip 1/3] synchronize_sched_expedited() primitive Paul E. McKenney
2009-06-24 16:47 ` [PATCH -tip 2/3] synchronize_sched_expedited() torture tests Paul E. McKenney
2009-06-24 16:48 ` [PATCH -tip 3/3] synchronize_sched_expedited() rcutorture doc Paul E. McKenney
2009-06-24 18:03 ` [PATCH -tip 0/3] expedited "big hammer" RCU grace periods Ingo Molnar
2009-06-24 18:44 ` Paul E. McKenney
2009-06-25 9:59 ` Ingo Molnar
2009-06-25 15:27 ` Paul E. McKenney
2009-06-25 16:47 ` Linus Torvalds [this message]
2009-06-25 17:54 ` Paul E. McKenney
2009-06-25 16:07 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=alpine.LFD.2.01.0906250944511.3605@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=jeff.chua.linux@gmail.com \
--cc=jengelh@medozas.de \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=r000n@r000n.net \
--cc=zbr@ioremap.net \
/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
all inboxes | Powered by JetHome®