mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Adrian Bunk <bunk@kernel.org>, David Miller <davem@davemloft.net>,
	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: Tue, 5 Aug 2008 16:51:10 -0700	[thread overview]
Message-ID: <20080805165110.f0991143.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080805233718.GB2514@lst.de>

On Wed, 6 Aug 2008 01:37:19 +0200 Christoph Hellwig <hch@lst.de> wrote:

> On Tue, Aug 05, 2008 at 11:03:30PM +0300, Adrian Bunk wrote:
> > Now that the driver is removed we should also remove the entry in 
> > Documentation/feature-removal-schedule.txt
> > 
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> > Acked-by: Christoph Hellwig <hch@lst.de>
> > 
> > ---
> > 
> > This patch has been sent on:
> > - 1 Mar 2008
> > 
> > 6d7882f6e844eaf6551b3a3708e01d1784916435 foobar
> > diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> > index c1d1fd0..a4530f0 100644
> > --- a/Documentation/feature-removal-schedule.txt
> > +++ b/Documentation/feature-removal-schedule.txt
> > @@ -19,15 +19,6 @@ Who:	Pavel Machek <pavel@suse.cz>
> >  
> >  ---------------------------
> >  
> > -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>
> > -
> > ----------------------------
> > -
> >  What:	Video4Linux API 1 ioctls and video_decoder.h from Video devices.
> >  When:	December 2008
> >  Files:	include/linux/video_decoder.h include/linux/videodev.h
> ---end quoted text---
>

(pop toasting repaired)

> This should really be easy enough for any merge window state, whoe wants
> to feed it to Linus?
> 

I have it queued for my next Linuswards batch.  I tend to push
non-code-related changes immediately.


  reply	other threads:[~2008-08-05 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 20:03 Adrian Bunk
2008-08-05 23:37 ` Christoph Hellwig
2008-08-05 23:51   ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-01 16:22 Adrian Bunk
2008-03-03  3:53 ` Christoph Hellwig

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=20080805165110.f0991143.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bunk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --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

Powered by JetHome