public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.53 : modules_install warnings
Date: Fri, 03 Jan 2003 10:54:36 +1100	[thread overview]
Message-ID: <20030103042650.54E652C09B@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 02 Jan 2003 07:57:36 CDT." <Pine.LNX.3.96.1030102075543.18246D-100000@gatekeeper.tmr.com>

In message <Pine.LNX.3.96.1030102075543.18246D-100000@gatekeeper.tmr.com> you w
rite:
> On Wed, 1 Jan 2003, Rusty Russell wrote:
> 
> > That's the point: they use cli, sti and save_flags.  All three were
> > eliminated in SMP completely independently of the module changes.
> > 
> > Hope I'm being clearer?
> 
> Okay, so there are two issues, the SMP issue noted and and changes which
> might be needed to make them work as modules. Gotit, thanks.

Nope, one issue.  The SMP issue.  There is no module issue here.
These are not the droids you are looking for. 8)

A patch to deprecate those functions might be in order.  But so might
a patch to just rip them out.

Hope that buries this,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      parent reply	other threads:[~2003-01-03  4:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 23:01 2.5.53 : modules_install warnings Frank Davis
2002-12-28 23:16 ` Arnaldo Carvalho de Melo
2002-12-29  6:09 ` Rusty Russell
2002-12-31  2:27   ` Bill Davidsen
2002-12-31  7:14     ` Rusty Russell
2002-12-31 14:24       ` Bill Davidsen
2002-12-31 23:34         ` Rusty Russell
2003-01-02 12:57           ` Bill Davidsen
2003-01-02 13:06             ` 2.5.x Configuration - about ISA Maciej Soltysiak
2003-01-02 17:13               ` Alan Cox
2003-01-02 23:54             ` Rusty Russell [this message]

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=20030103042650.54E652C09B@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=davidsen@tmr.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