From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Garzik <jeff@garzik.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Val Henson <val_henson@linux.intel.com>,
netdev@vger.kernel.org, Helge Deller <deller@parisc-linux.org>,
Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [PATCH] [TULIP] Fix section mismatch in de2104x.c
Date: Fri, 6 Oct 2006 13:54:47 -0600 [thread overview]
Message-ID: <20061006195447.GQ2563@parisc-linux.org> (raw)
In-Reply-To: <4526B21E.8060408@garzik.org>
On Fri, Oct 06, 2006 at 03:44:30PM -0400, Jeff Garzik wrote:
> Matthew Wilcox wrote:
> >On Fri, Oct 06, 2006 at 03:18:33PM -0400, Jeff Garzik wrote:
> >>This device will never ever meet a platform where it can be hotplugged.
> >
> >According to a FreeBSD list from 1995, you could get these chips on a PCI
> >card from several different vendors.
> >
>
> Yes, they are ancient 32-bit PCI cards, which will never make an
> appearance on a PCI hotplug platform. So, it's wasteful to support
> hotplug in code that will never be hotplugged (as I've said for years).
Sorry, you're saying that anyone who has found one of these cards and
wants to plug them into a hotplug slot in their shiny new server is just
SOL? That makes no sense, Jeff. We've fixed *so* many old drivers to
confirm to these rules, why's this one so special? I'd understand if it
were only found on motherboards, but it can be found on cards.
Plus it silences a warning. Isn't that enough reason of its own?
next prev parent reply other threads:[~2006-10-06 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 18:12 [PATCH] [TULIP] Fix section mismatch in de2104x.c Matthew Wilcox
2006-10-06 18:03 ` Stephen Hemminger
2006-10-06 19:18 ` Jeff Garzik
2006-10-06 19:25 ` Matthew Wilcox
2006-10-06 19:44 ` Jeff Garzik
2006-10-06 19:54 ` Matthew Wilcox [this message]
2006-10-06 20:11 ` Jeff Garzik
2006-10-06 18:39 ` Jeff Garzik
2006-10-06 18:45 ` Matthew Wilcox
2006-10-06 18:50 ` Jeff Garzik
2006-10-06 19:25 ` More info on section mismatches (was Re: [PATCH] [TULIP] Fix section mismatch in de2104x.c) Valerie Henson
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=20061006195447.GQ2563@parisc-linux.org \
--to=matthew@wil.cx \
--cc=deller@parisc-linux.org \
--cc=jeff@garzik.org \
--cc=kyle@parisc-linux.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=val_henson@linux.intel.com \
/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).