From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Hugh Dickins <hugh@veritas.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport install_page
Date: Tue, 21 Feb 2006 14:34:33 +0000 [thread overview]
Message-ID: <1140532473.840.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20060221141341.GW4661@stusta.de>
On Maw, 2006-02-21 at 15:13 +0100, Adrian Bunk wrote:
> This means it has only bloated the kernel for two and a half years
> for nearly everyone.
Wouldn't it be more productive to just shave 30 bytes off some other
function and make it faster instead of moaning about every single export
symbol that is provided even when its intentionally part of a complete
API ?
next prev parent reply other threads:[~2006-02-21 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 22:37 Adrian Bunk
2006-02-21 10:38 ` Christoph Hellwig
2006-02-21 12:49 ` Hugh Dickins
2006-02-21 14:13 ` Adrian Bunk
2006-02-21 14:34 ` Alan Cox [this message]
2006-02-21 14:36 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 19:19 Adrian Bunk
2006-02-16 17:03 Adrian Bunk
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=1140532473.840.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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