From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] net/netlink/: possible cleanups
Date: Tue, 18 Apr 2006 19:48:41 +0100 [thread overview]
Message-ID: <1145386121.21723.28.camel@localhost.localdomain> (raw)
In-Reply-To: <20060418141946.GC11582@stusta.de>
On Maw, 2006-04-18 at 16:19 +0200, Adrian Bunk wrote:
> OTOH, we also have to always check whether users are expected soon (and
> recheck whether there are really users after some time) since every
> single export makes the kernel larger for nearly everyone.
Of course fixing the amount of memory used by an EXPORT_SYMBOL would be
far more productive.
next prev parent reply other threads:[~2006-04-18 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 16:27 [RFC: 2.6 patch] net/netlink/: possible cleanups Adrian Bunk
2006-04-13 20:26 ` David S. Miller
2006-04-14 10:32 ` Adrian Bunk
2006-04-14 10:56 ` Evgeniy Polyakov
2006-04-18 14:19 ` Adrian Bunk
2006-04-18 18:48 ` Alan Cox [this message]
2006-04-18 19:09 ` Adrian Bunk
2006-04-19 0:02 ` Philip Craig
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=1145386121.21723.28.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).