From: "Barry K. Nathan" <barryn@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, domen@coderock.org
Subject: pcnet32 oops patches (was Re: 2.6.0-test4-mm1)
Date: Sun, 24 Aug 2003 23:16:54 -0700 [thread overview]
Message-ID: <20030825061654.GB3562@ip68-4-255-84.oc.oc.cox.net> (raw)
In-Reply-To: <20030824171318.4acf1182.akpm@osdl.org>
On Sun, Aug 24, 2003 at 05:13:18PM -0700, Andrew Morton wrote:
> +pcnet32-unregister_pci-fix.patch
>
> rmmod crash fix
Here's another (conflicting) patch by the same author:
http://bugme.osdl.org/attachment.cgi?id=684&action=view
There's an oops I'm having (bugzilla bug 976 -- basically, after
modprobing pcnet32 on a box without pcnet32 hardware, the next ethernet
driver to be modprobed blows up) which is not fixed by the patch in
test4-mm1, but which is fixed by attachment 684...
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2003-08-25 6:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 0:13 2.6.0-test4-mm1 Andrew Morton
2003-08-25 6:16 ` Barry K. Nathan [this message]
2003-08-25 11:00 ` pcnet32 oops patches (was Re: 2.6.0-test4-mm1) Domen Puncer
2003-08-25 17:30 ` 2.6.0-test4-mm1: wl3501_cs.c doesn't compile Adrian Bunk
2003-08-25 17:46 ` Arnaldo Carvalho de Melo
2003-08-25 18:24 ` Arnaldo Carvalho de Melo
2003-08-25 18:39 ` Arnaldo Carvalho de Melo
2003-08-25 22:01 ` Adrian Bunk
2003-08-26 15:22 ` Arnaldo Carvalho de Melo
2003-08-25 19:37 ` [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption Barry K. Nathan
2003-08-25 19:45 ` Andrew Morton
2003-08-25 22:54 ` Steve Lord
2003-08-26 10:14 ` Andrew Morton
2003-08-26 11:01 ` Suparna Bhattacharya
2003-08-26 17:44 ` Andrew Morton
2003-08-26 17:57 ` Steve Lord
2003-08-26 18:34 ` Andrew Morton
2003-08-25 23:10 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 10:08 ` 2.6.0-test4-mm1 William Lee Irwin III
2003-08-26 14:23 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 14:32 ` 2.6.0-test4-mm1 William Lee Irwin III
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=20030825061654.GB3562@ip68-4-255-84.oc.oc.cox.net \
--to=barryn@pobox.com \
--cc=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).