From: Alan Cox <alan@redhat.com>
To: kaos@ocs.com.au (Keith Owens)
Cc: dwmw2@infradead.org (David Woodhouse),
vojtech@suse.cz (Vojtech Pavlik), alan@redhat.com (Alan Cox),
torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make agpsupport work with modversions
Date: Sat, 28 Oct 2000 05:40:28 -0400 (EDT) [thread overview]
Message-ID: <200010280940.e9S9eSx02362@devserv.devel.redhat.com> (raw)
In-Reply-To: <5122.972699496@ocs3.ocs-net> from "Keith Owens" at Oct 28, 2000 01:18:16 PM
> cc list trimmed. Nobody has come up with a "must have" reason for
> get_module_symbol and that interface is broken as designed. I will be
Nobody has come up with a 'must break existing sane code' reason either.
> will allow two objects to pass data to each other, it will not matter
> whether the objects are both modules, one module and one built in (in
> either order) or both built in. When modules are involved there will
> be full module locking.
You have no consensus on this. None at all. It is also past the 2.4test
point for making this change.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-28 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001019102722.B9057@suse.cz>
2000-10-26 22:21 ` [PATCH] Make agpsupport work with modversions Alan Cox
2000-10-26 22:55 ` Vojtech Pavlik
2000-10-27 13:25 ` David Woodhouse
2000-10-28 2:18 ` Keith Owens
2000-10-28 6:58 ` Andrew Morton
2000-10-28 9:40 ` Alan Cox [this message]
2000-10-28 9:55 ` Keith Owens
2000-10-28 10:07 ` Alan Cox
2000-10-28 10:02 ` Alan Cox
2000-10-28 10:08 ` Keith Owens
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=200010280940.e9S9eSx02362@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=vojtech@suse.cz \
/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