LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] final SCSI updates for 2.6.24 merge window
Date: Thu, 07 Feb 2008 17:14:44 -0800 [thread overview]
Message-ID: <1202433284.31361.29.camel@brick> (raw)
In-Reply-To: <1202432873.3171.58.camel@localhost.localdomain>
On Thu, 2008-02-07 at 19:07 -0600, James Bottomley wrote:
> On Thu, 2008-02-07 at 17:04 -0800, Harvey Harrison wrote:
> > On Thu, 2008-02-07 at 18:56 -0600, James Bottomley wrote:
> > > Quite a bit of this is fixing things broken previously (the advansys fix
> > > is still pending resolution, but I'll send it as an -rc fix when we have
> > > it). There's the final elimination of all drivers that are esp based
> > > but don't use the scsi_esp core (that's mostly m68k and alpha). Plus
> > > the usual bunch of driver updates and the addition of a new enclosure
> > > services driver and the corresponding ULD.
> > >
> > > The patch is available from:
> > >
> >
> > I'm going to guess that this is the entry in feature-removal.txt
> > that need an update then:
> >
> > ---------------------------
> >
> > What: old NCR53C9x driver
> > When: October 2007
> > Why: Replaced by the much better esp_scsi driver. Actual low-level
> > driver can be ported over almost trivially.
> > Who: David Miller <davem@davemloft.net>
> > Christoph Hellwig <hch@lst.de>
>
> Not immediately ... I anticipate a few "where'd my driver go?" type
> questions from m68k for which this provides a useful reference to point
> to ...
>
> James
>
>
Well, if not removed, how about updated:
What: old NCR53C9x driver
When: Removed Feb 2008
Why: Replaced by the much better esp_scsi driver. Actual low-level
driver can be ported over almost trivially.
Who: James Bottomley <James.Bottomley@HansenPartnership.com>
Cheers,
Harvey
next prev parent reply other threads:[~2008-02-08 1:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 0:56 [GIT PATCH] final SCSI updates for 2.6.24 merge window James Bottomley
2008-02-08 1:04 ` Harvey Harrison
2008-02-08 1:07 ` James Bottomley
2008-02-08 1:14 ` Harvey Harrison [this message]
2008-02-08 9:03 ` Geert Uytterhoeven
2008-02-08 16:37 ` James Bottomley
2008-02-11 21:13 ` Harvey Harrison
2008-02-11 22:02 ` James Bottomley
2008-02-08 1:37 ` James Bottomley
2008-02-08 3:53 ` FUJITA Tomonori
2008-02-08 2:46 ` Andrew Morton
2008-02-08 3:11 ` Linus Torvalds
2008-02-08 5:05 ` Christoph Hellwig
2008-02-08 3:16 ` James Bottomley
2008-02-08 3:24 ` Andrew Morton
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=1202433284.31361.29.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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).