From: Rusty Russell <rusty@rustcorp.com.au>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>, `@samba.org
Subject: Re: 2.5.53 : modules_install warnings
Date: Tue, 31 Dec 2002 18:14:55 +1100 [thread overview]
Message-ID: <20021231074756.2B9AC2C10B@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 30 Dec 2002 21:27:01 CDT." <Pine.LNX.3.96.1021230212600.8353B-100000@gatekeeper.tmr.com>
In message <Pine.LNX.3.96.1021230212600.8353B-100000@gatekeeper.tmr.com> you wr
ite:
> On Sun, 29 Dec 2002, Rusty Russell wrote:
>
> > In message <Pine.LNX.4.44.0212281758230.839-100000@linux-dev> you write:
> > > Hello all,
> > > I received the following warnings while a 'make modules_install'. It
> > > looks like there are a few more locking changes that need to be made. :)
> >
> > This is SMP, right? Those warnings are perfectly correct (yes, those
> > files need updating).
>
> Any guess when you'll get them fixed?
I've discovered an interesting (but kinda obvious) phenomenon. If you
destabilize some part of the kernel, it becomes the natural suspect
for problems.
The corollary is, I'm getting more reports on kernel "module" bugs
which are not actually my fault at all (and some, like erroneous
__init sections, which the new module code just shows up).
This is one: these drivers are actually broken. They give warnings on
compile, they won't link when compiled in, and they won't insert as
modules.
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-12-31 7:39 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 [this message]
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 ` 2.5.53 : modules_install warnings Rusty Russell
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=20021231074756.2B9AC2C10B@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=`@samba.org \
--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