From: Adrian Bunk <bunk@stusta.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: still curious about that CONFIG_FORCED_INLINING option
Date: Tue, 10 Apr 2007 00:37:27 +0200 [thread overview]
Message-ID: <20070409223727.GA28370@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0704091319020.20218@CPE00045a9c397f-CM001225dbafb6>
On Mon, Apr 09, 2007 at 01:21:27PM -0400, Robert P. J. Day wrote:
>
> i'm curious -- has there been any decision about the config option
> of FORCED_INLINING? the feature removal file suggests it should have
> disappeared last year. is it still doing something useful?
It never did anything.
> rday
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2007-04-09 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 17:21 still curious about that CONFIG_FORCED_INLINING option Robert P. J. Day
2007-04-09 22:37 ` Adrian Bunk [this message]
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=20070409223727.GA28370@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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