public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Simon Evans <spse@secret.org.uk>,
	linux-pcmcia@lists.infradead.org, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken MTD_PCMCIA driver
Date: Tue, 28 Nov 2006 22:16:27 +0000	[thread overview]
Message-ID: <1164752187.14595.20.camel@pmac.infradead.org> (raw)
In-Reply-To: <20061118214056.GB31879@stusta.de>

On Sat, 2006-11-18 at 22:40 +0100, Adrian Bunk wrote:
> The MTD_PCMCIA driver has:
> - already been marked as BROKEN in 2.6.0 three years ago and
> - is still marked as BROKEN.
> 
> Drivers that had been marked as BROKEN for such a long time seem to be
> unlikely to be revived in the forseeable future.

Actually, there's hardware currently on its way to me, and I plan to fix
this driver fairly soon.

> But if anyone wants to ever revive this driver, the code is still
> present in the older kernel releases.

I'm unconvinced by that argument in the general case. People don't go
looking back through git history, do they? Drivers such as this don't
really do any harm as they are, and they're _much_ easier to find when
someone does want to fix them up.

-- 
dwmw2

  reply	other threads:[~2006-11-28 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 21:40 [RFC: 2.6 patch] remove the broken MTD_PCMCIA driver Adrian Bunk
2006-11-28 22:16 ` David Woodhouse [this message]
2006-11-30  7:09   ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-11-25 19:15 Adrian Bunk
2006-11-26  9:40 ` Artem Bityutskiy

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=1164752187.14595.20.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=spse@secret.org.uk \
    /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