From: David Woodhouse <dwmw2@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Pekka Savola <pekkas@netcore.fi>,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: IPv6: the same address can be added multiple times
Date: Mon, 14 May 2001 11:48:53 +0100 [thread overview]
Message-ID: <27266.989837333@redhat.com> (raw)
In-Reply-To: <15103.18224.265350.877968@pizda.ninka.net>
In-Reply-To: <15103.18224.265350.877968@pizda.ninka.net> <200105131759.VAA27768@ms2.inr.ac.ru> <Pine.LNX.4.33.0105132319120.3026-100000@netcore.fi>
davem@redhat.com said:
> There is this growing (think growing as in "fungus") set of thinking
> that just because something can be misused, this is an argument
> against it even existing.
> I think this is wrong. I'm seeing it a lot, especially on this list,
> and it's becomming a real concern at least to me.
The removal of the perfectly sane get_module_symbol() and replacement with
a less useful function which looks stuff up in a dynamic table instead of a
static table built at link time is an example of this. Now I have horrible
link order dependencies in code which was previously relatively clean. It
sucks, and there was absolutely no reason for it.
The fact that it was done so late in 2.4-test without even a period of
marking the original sane version as deprecated made it even worse.
Thinks... if I violently abuse inter_module_crap() will it suffer the same
fate and can I replace it with get_module_symbol() again? :)
--
dwmw2
next prev parent reply other threads:[~2001-05-14 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0105031202080.13012-100000@netcore.fi>
2001-05-13 17:59 ` IPv6: the same address can be added multiple times kuznet
2001-05-13 20:26 ` Pekka Savola
2001-05-14 2:47 ` David S. Miller
2001-05-14 7:42 ` Kai Henningsen
2001-05-14 10:48 ` David Woodhouse [this message]
2001-05-14 18:21 ` kuznet
2001-05-18 14:00 ` Pekka Savola
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=27266.989837333@redhat.com \
--to=dwmw2@infradead.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pekkas@netcore.fi \
/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