From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Gergely Madarasz <gorgo@itc.hu>, netdev@oss.sgi.com
Subject: Re: comx drivers in 2.6
Date: Thu, 17 Jul 2003 19:42:16 -0400 [thread overview]
Message-ID: <3F173458.6060405@pobox.com> (raw)
In-Reply-To: <20030717163337.78d123c0.shemminger@osdl.org>
Stephen Hemminger wrote:
> It looks like the comx drivers never got updated for 2.5/2.6. Some
> obvious issues are:
> - lots of use of /proc files without setting the owner field.
> - still using cli/sti
> - no SMP locking on the linked list (which could be changed to list macros)
> of hardware and protocols.
>
> Just bumped into this while trying to inspect for all the last possible
> broken usage of net_device structure. It is too far behind to address
> those issues.
Submit a patch to mark these CONFIG_OBSOLETE. AFAIK nobody has cared
for most of them since 2.2... (munich is an exception)
Jeff
next prev parent reply other threads:[~2003-07-17 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 23:33 comx drivers in 2.6 Stephen Hemminger
2003-07-17 23:42 ` Jeff Garzik [this message]
2003-07-18 19:36 ` Stephen Hemminger
2003-07-19 8:14 ` Gergely Madarasz
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=3F173458.6060405@pobox.com \
--to=jgarzik@pobox.com \
--cc=gorgo@itc.hu \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).