From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, viro@ZenIV.linux.org.uk
Subject: Re: CONFIG_OPTIMIZE_INLINING
Date: Sat, 26 Apr 2008 23:08:07 -0700 (PDT) [thread overview]
Message-ID: <20080426.230807.144232984.davem@davemloft.net> (raw)
In-Reply-To: <20080427055943.GA16290@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 27 Apr 2008 07:59:43 +0200
> ... as i saw no reason why this feature, which i found rather useful,
> should be delayed another year or so. I'd be more than happy to promote
> this feature back to lib/Kconfig.debug, sparc64 interest would make that
> a strong argument.
So you caved in to FUD in order to pad your commit and signoff count?
Because anyone who is paying attention can see clearly that you're
trying to push as much stuff as quickly as possible into Linus's tree
with your singoffs and authorship on it this merge window.
Gee, I wonder why...
next prev parent reply other threads:[~2008-04-27 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 4:55 CONFIG_OPTIMIZE_INLINING David Miller
2008-04-27 5:59 ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 6:08 ` David Miller [this message]
2008-04-27 8:20 ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 9:10 ` CONFIG_OPTIMIZE_INLINING SL Baur
2008-04-27 9:16 ` CONFIG_OPTIMIZE_INLINING Dave Airlie
2008-04-27 9:21 ` CONFIG_OPTIMIZE_INLINING David Miller
2008-04-27 12:13 ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 11:22 ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 17:25 ` CONFIG_OPTIMIZE_INLINING Pavel Machek
2008-04-28 10:42 ` CONFIG_OPTIMIZE_INLINING Adrian Bunk
2008-04-27 6:26 ` CONFIG_OPTIMIZE_INLINING Christoph Hellwig
2008-04-27 10:56 ` CONFIG_OPTIMIZE_INLINING Sam Ravnborg
2008-04-27 6:02 ` CONFIG_OPTIMIZE_INLINING Sam Ravnborg
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=20080426.230807.144232984.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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