linux-kernel - Re: [2.6 patch] remove the broken ETRAX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 15 Apr 2008 23:35:20 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Mikael Starvik <mikael.starvik@...s.com>,
	Jesper Nilsson <Jesper.Nilsson@...s.com>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [2.6 patch] remove the broken ETRAX_IDE driver

On Monday 14 April 2008, Adrian Bunk wrote:
> On Mon, Apr 14, 2008 at 02:50:19PM +0200, Mikael Starvik wrote:
> > You can remove it for now and we will resubmit a new if/when we get around
> > to fix it.
> 
> Thanks for the confirmation.
> 
> > /Mikael
> 
> cu
> Adrian
> 
> BTW: If/When you'll get around to work on it, please consider using
>      libata instead.
> 
> 
> <--  snip  -->
> 
> 
> ETRAX_IDE was marked as broken last year with the comment
> "it doesn't even compile currently".
> 
> Remove it since it won't get fixed in the near future.
> 
> Signed-off-by: Adrian Bunk <bunk@...nel.org>

applied

[ I ported the patch over IDE tree (it becomes honorable patch #250)
  so it deletes the most recent ide-cris version - even though the
  driver was marked as BROKEN I kept updating it and it is the best
  starting point if somebody would like to revive it in the future
  (or port it to libata). ]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/