public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "D. ShadowWolf" <dhazelton@enter.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inter_module_get and __symbol_get
Date: Mon, 01 Aug 2005 02:04:06 +0100	[thread overview]
Message-ID: <1122858246.15622.12.camel@localhost.localdomain> (raw)
In-Reply-To: <200507310027.18484.dhazelton@enter.net>

On Sul, 2005-07-31 at 00:27 -0400, D. ShadowWolf wrote:
> On this topic I have to weigh in that I just subscribed to the kernel list 
> because I have had to undo a modification made to the kernel around version 
> 2.6.10 that stopped the export of 'inter_module_get'.  To me it appears that 
> some kernel developers forget that there are those of us out there who do not 
> have broadband connections and are shafted with low-end hardware.

inter_module_* are going away. It was always a badly designed interface
and the new module code no longer requires it. 

Alan



  reply	other threads:[~2005-08-01  0:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  4:27 inter_module_get and __symbol_get D. ShadowWolf
2005-08-01  1:04 ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-06 21:32 Terence Ripperda
2005-01-06 21:57 ` Brian Gerst
2005-01-06 22:51   ` Terence Ripperda
2005-01-08  4:00     ` Jon Smirl
2005-01-12 19:37       ` Terence Ripperda
2005-01-12 22:21         ` Brian Gerst
2005-01-08  3:10   ` Keith Owens
2005-01-24 22:36     ` David Mosberger
2005-01-24 22:44       ` Keith Owens
2005-01-24 22:52         ` David Mosberger
2005-01-24 22:54           ` Keith Owens
2005-01-24 22:58             ` David Mosberger
2005-01-24 23:03               ` Keith Owens
2005-01-25  1:01                 ` Jon Smirl
2005-01-24 23:19           ` Jon Smirl
2005-01-24 23:23             ` David Mosberger
2005-01-25  5:31         ` Terence Ripperda
2005-01-25  5:59           ` Chris Wedgwood

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=1122858246.15622.12.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dhazelton@enter.net \
    --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