public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Brian Strand <bstrand@switchmanagement.com>
Cc: John Weber <weber@nyc.rr.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: PCI Hotplug and Linux 2.5.4-pre2
Date: Thu, 7 Feb 2002 19:50:28 +0100	[thread overview]
Message-ID: <20020207195028.O22451@suse.de> (raw)
In-Reply-To: <3C62C4AB.3040109@nyc.rr.com> <3C62C831.9010302@switchmanagement.com>
In-Reply-To: <3C62C831.9010302@switchmanagement.com>; from bstrand@switchmanagement.com on Thu, Feb 07, 2002 at 10:32:17AM -0800

On Thu, Feb 07, 2002 at 10:32:17AM -0800, Brian Strand wrote:

 > I vote yes; I always turn on as many modularizable chunks as possible, 
 > to increase "compile coverage".  And we all know if it compiles, it 
 > works, right?

 I hope that was sarcasm 8-) Some things such as the NCR5380 'fixes'
 in Linus tree have put the driver into a state where it compiles and
 maybe even runs, but it's almost guaranteed to corrupt.  There's
 a more complete set of fixes for some of these problems in my tree,
 but alas, doesn't compile..

 Numerous other bio related problems have been reported and had
 'quick fixes' offered for them which turn out to be worse than
 a non-compiling driver.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2002-02-07 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 18:17 PCI Hotplug and Linux 2.5.4-pre2 John Weber
2002-02-07 18:23 ` Greg KH
2002-02-07 18:32 ` Brian Strand
2002-02-07 18:50   ` Dave Jones [this message]

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=20020207195028.O22451@suse.de \
    --to=davej@suse.de \
    --cc=bstrand@switchmanagement.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weber@nyc.rr.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