From: Jeff Muizelaar <muizelaar@rogers.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] NE2000 driver updates
Date: Thu, 01 May 2003 12:53:59 -0400 [thread overview]
Message-ID: <3EB15127.2060409@rogers.com> (raw)
The first two patches are retransmits of the original PnP api patches
updated to apply to a current tree.
The third patch is more of an RFC. It consolidates the creation/removal
of the driver between the PnP code and the plain ISA code. In doing so
it changes the net_device allocation from static to dynamic and allows
PnP support when the driver is compiled in. This is probably how things
will eventually have to be if there is ever driver model support for
plain ISA devices.
The forth patch gets rid of the use of dev->mem_end as a bad flag.
Caveats:
It appears that the patch will break any autoprobe ordering because it no
longer uses Space.c when compiled into the kernel.
Data size of object goes up about 100 bytes.
-Jeff
next reply other threads:[~2003-05-01 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 16:53 Jeff Muizelaar [this message]
2003-05-01 16:58 ` [PATCH 1/4] NE2000 driver updates Jeff Muizelaar
2003-05-01 16:59 ` [PATCH 2/4] " Jeff Muizelaar
2003-05-01 16:59 ` [PATCH 3/4] " Jeff Muizelaar
2003-05-01 17:08 ` Jeff Muizelaar
2003-05-01 17:47 ` [PATCH 4/4] " Jeff Muizelaar
2003-05-01 19:23 ` [PATCH 0/4] " Alan Cox
2003-05-01 23:29 ` Jeff Muizelaar
2003-05-02 14:01 ` Alan Cox
2003-05-02 15:57 ` Jeff Garzik
2003-05-02 15:24 ` Alan Cox
2003-05-02 16:29 ` Riley Williams
2003-05-14 2:01 ` Jeff Muizelaar
2003-05-14 21:51 ` Adam Belay
2003-05-15 3:01 ` Jeff Muizelaar
[not found] <BKEGKPICNAKILKJKMHCACEOMCPAA.Riley@Williams.Name>
2003-05-14 11:02 ` Alan Cox
2003-05-14 23:11 ` Jeff Muizelaar
2003-05-14 22:46 ` Jeff Muizelaar
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=3EB15127.2060409@rogers.com \
--to=muizelaar@rogers.com \
--cc=jgarzik@pobox.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