From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965888AbXCVJfX (ORCPT ); Thu, 22 Mar 2007 05:35:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965900AbXCVJfW (ORCPT ); Thu, 22 Mar 2007 05:35:22 -0400 Received: from mx2.suse.de ([195.135.220.15]:50149 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965888AbXCVJfV convert rfc822-to-8bit (ORCPT ); Thu, 22 Mar 2007 05:35:21 -0400 From: Oliver Neukum Organization: Novell To: "roland" 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 User-Agent: KMail/1.9.1 Cc: linux-kernel@vger.kernel.org, bunk@stusta.de References: <052c01c76c62$78f7f7a0$eeeea8c0@aldipc> In-Reply-To: <052c01c76c62$78f7f7a0$eeeea8c0@aldipc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200703221035.19832.oneukum@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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