From: Christoph Hellwig <hch@lst.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: David Miller <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] feature-removal-schedule.txt: remove the NCR53C9x entry
Date: Mon, 3 Mar 2008 04:53:06 +0100 [thread overview]
Message-ID: <20080303035306.GA21743@lst.de> (raw)
In-Reply-To: <20080301162246.GW25835@cs181133002.pp.htv.fi>
On Sat, Mar 01, 2008 at 06:22:46PM +0200, Adrian Bunk wrote:
> Now that the driver is removed we should also remove the entry in
> Documentation/feature-removal-schedule.txt
ACK
next prev parent reply other threads:[~2008-03-03 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:22 [2.6 patch] feature-removal-schedule.txt: remove the NCR53C9x entry Adrian Bunk
2008-03-03 3:53 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 20:03 Adrian Bunk
2008-08-05 23:37 ` Christoph Hellwig
2008-08-05 23:51 ` 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=20080303035306.GA21743@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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