linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Matthew Jacob <mjacob@feral.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Justin T. Gibbs" <gibbs@scsiguy.com>,
	Mike Brown <mbrown@emc.com>,
	bferjul@emc.com, jkrasner@emc.com, conway_heather@emc.com,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Ghost devices being reported with AIC7XXX version 6.2.6
Date: Thu, 31 Oct 2002 15:43:09 -0500	[thread overview]
Message-ID: <20021031204309.GH30047@redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0210311220550.23076-100000@beppo>

On Thu, Oct 31, 2002 at 12:27:44PM -0800, Matthew Jacob wrote:
> > On Thu, Oct 31, 2002 at 12:04:16PM -0800, Matthew Jacob wrote:
> > > 
> > > *blush*
> > > 
> > > I was actually going to start finally working 2.5 next week (don't hit
> > > me! don't hit me)
> > 
> > Hehehe!  Going to start after the feature freeze is already over, makes it 
> > kind of hard to get anything new in doesn't it ;-)
> 
> Well, look- doing feature freezes early is all well and swell, but
> remember that a lot of us out here, if we get any work stuff at all for
> Linux, has us concentrate on 2.4, or even 2.2.

Yes, I know, that's why there was a wink-smiley there.

> driver subsystems are candidates for late binding and late changing
> because they are typically isolated areas.

As well as they are here.  At least driver updates anyway.  Driver 
subsystem changes are a bit harder to get in, especially if they stand a 
chance of breaking other working drivers.


-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  parent reply	other threads:[~2002-10-31 20:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 17:03 [PATCH] Ghost devices being reported with AIC7XXX version 6.2.6 Mike Brown
2002-10-31 18:03 ` Justin T. Gibbs
2002-10-31 18:28   ` Matthew Jacob
2002-10-31 19:21     ` Alan Cox
2002-10-31 19:30       ` Matthew Jacob
2002-10-31 20:03         ` Doug Ledford
2002-10-31 20:04           ` Matthew Jacob
2002-10-31 20:17             ` Doug Ledford
2002-10-31 20:27               ` Matthew Jacob
2002-10-31 20:40                 ` Matthew Jacob
2002-10-31 20:43                 ` Doug Ledford [this message]
2002-11-01 13:00               ` Alan Cox
2002-11-01  1:41       ` Patrick Mansfield
2002-10-31 20:07   ` Doug Ledford
2002-10-31 20:26     ` Matthew Jacob
2002-10-31 20:38       ` Doug Ledford
2002-10-31 20:39         ` Matthew Jacob
2002-10-31 20:40         ` Mike Brown
2002-10-31 20:41           ` Matthew Jacob
2002-10-31 21:00             ` Mike Brown
2002-10-31 21:14               ` James Bottomley
2002-10-31 20:38     ` Mike Brown
2002-10-31 21:25       ` Doug Ledford

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=20021031204309.GH30047@redhat.com \
    --to=dledford@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bferjul@emc.com \
    --cc=conway_heather@emc.com \
    --cc=gibbs@scsiguy.com \
    --cc=jkrasner@emc.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mbrown@emc.com \
    --cc=mjacob@feral.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).