From: Oliver Neukum <oneukum@suse.de>
To: "roland" <devzero@web.de>
Cc: linux-kernel@vger.kernel.org, bunk@stusta.de
Subject: Re: [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h
Date: Thu, 22 Mar 2007 10:35:19 +0100 [thread overview]
Message-ID: <200703221035.19832.oneukum@suse.de> (raw)
In-Reply-To: <052c01c76c62$78f7f7a0$eeeea8c0@aldipc>
Am Donnerstag, 22. März 2007 10:14 schrieb roland:
> i wonder if there still exist any of those devices in functional state in
> this world, at least not attached to some system being able to boot
> 2.6.21+ - so, maybe mcdx driver is something for
> Documentation/feature-removal-schedule.txt , being removed in 2.6.25 or so
> after being announced for some time (i.e. driver telling "i will be gone
> soon, go spend those $15 to get a new drive") ?
Why? For the sake of sheer removal?
Regards
Oliver
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
This signature is a legal requirement
next prev parent reply other threads:[~2007-03-22 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 9:14 [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h roland
2007-03-22 9:35 ` Oliver Neukum [this message]
2007-03-23 22:59 ` roland
2007-03-23 23:09 ` Adrian Bunk
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=200703221035.19832.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=bunk@stusta.de \
--cc=devzero@web.de \
--cc=linux-kernel@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 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.