From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
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: Sun, 27 Apr 2008 07:59:43 +0200 [thread overview]
Message-ID: <20080427055943.GA16290@elte.hu> (raw)
In-Reply-To: <20080426.215513.141243565.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> Ingo, why the heck is this hiding under arch/x86/ and not in
> lib/Kconfig.debug where it belongs?
>
> x86: add optimized inlining
>
> If there are platforms that can't handle it, we can add a conditional
> to lib/Kconfig.debug, but by default it should be made available
> generically.
>
> Where did this original patch get posted for review and discussion?
>
> Tell me where!?!?!
here, two months ago:
http://lkml.org/lkml/2008/3/3/122
i made it x86-only due to this FUD that went against it:
"messing with a global #define in a way that the results on 24
architectures with 7 different releases of gcc would be
unpredictable."
... 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.
and here is the pull request that i posted to lkml, with the full patch
included as well:
http://www.gossamer-threads.com/lists/linux/kernel/911104?page=last
> The only references I see is where Stephen Rothwell complained that it
> broke the powerpc build, and then on the git commit list when Linus
> sucked this crud in.
i think there must something wrong about your lkml feed.
Ingo
next prev parent reply other threads:[~2008-04-27 6:00 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 ` Ingo Molnar [this message]
2008-04-27 6:08 ` CONFIG_OPTIMIZE_INLINING David Miller
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=20080427055943.GA16290@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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