From: Harvey Harrison <harvey.harrison@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: rae l <crquan@gmail.com>, Pavel Machek <pavel@suse.cz>,
David Miller <davem@davemloft.net>,
Dominik Brodowski <linux@brodo.de>, Adrian Bunk <bunk@stusta.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Nick Piggin <npiggin@suse.de>, Len Brown <len.brown@intel.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: many items in Documentation/feature-removal-schedule.txt have expired, please update
Date: Thu, 20 Mar 2008 09:15:52 -0700 [thread overview]
Message-ID: <1206029752.17059.1.camel@brick> (raw)
In-Reply-To: <20080320132543.GA11149@lst.de>
On Thu, 2008-03-20 at 14:25 +0100, Christoph Hellwig wrote:
> On Thu, Mar 20, 2008 at 09:22:29PM +0800, rae l wrote:
> > 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>
>
> This one is long gone, probably just needs a doc patch.
>
I sent a patch to James Bottomley after the removal a few weeks ago, he
said he wanted the message to stay for a release in case someone goes
looking for the driver.
Harvey
next prev parent reply other threads:[~2008-03-20 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:22 many items in Documentation/feature-removal-schedule.txt have expired, please update rae l
2008-03-20 13:25 ` Christoph Hellwig
2008-03-20 16:15 ` Harvey Harrison [this message]
2008-03-20 20:22 ` Pavel Machek
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=1206029752.17059.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arjan@linux.intel.com \
--cc=bunk@stusta.de \
--cc=crquan@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=npiggin@suse.de \
--cc=pavel@suse.cz \
--cc=shemminger@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