From: Brad Boyer <flar@allandria.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: funaho@jurai.org, linux-mac68k@mac.linux-m68k.org,
geert@linux-m68k.org, zippel@linux-m68k.org,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken BLK_DEV_SWIM_IOP driver
Date: Sun, 19 Nov 2006 22:41:06 -0800 [thread overview]
Message-ID: <20061120064106.GA25209@cynthia.pants.nu> (raw)
In-Reply-To: <20061120210654.GC31879@stusta.de>
On Mon, Nov 20, 2006 at 10:06:54PM +0100, Adrian Bunk wrote:
> The BLK_DEV_SWIM_IOP 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.
>
> But if anyone wants to ever revive this driver, the code is still
> present in the older kernel releases.
Feel free to remove this one. It was never in a state that worked, but
was added to the tree anyway. I tried to fix it when I was given a
copy of the documentation, but it needed more work than I initially
expected. The initial version that was in the tree could only detect
the drives, and the only thing I added other than some bug fixes was
support for the eject ioctl. The read/write path in the driver is
missing the actual data transfer routines, and is therefore not in
a working state.
For the record, I believe the linux-mac68k list is dead.
Brad Boyer
flar@allandria.com
prev parent reply other threads:[~2006-11-20 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 21:06 [RFC: 2.6 patch] remove the broken BLK_DEV_SWIM_IOP driver Adrian Bunk
2006-11-20 6:41 ` Brad Boyer [this message]
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=20061120064106.GA25209@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=bunk@stusta.de \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mac68k@mac.linux-m68k.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.