All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Mikael Starvik <mikael.starvik@axis.com>,
	Jesper Nilsson <Jesper.Nilsson@axis.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] remove the broken ETRAX_IDE driver
Date: Tue, 15 Apr 2008 23:35:20 +0200	[thread overview]
Message-ID: <200804152335.21101.bzolnier@gmail.com> (raw)
In-Reply-To: <20080414184213.GB6695@cs181133002.pp.htv.fi>

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@kernel.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). ]

      reply	other threads:[~2008-04-15 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 18:36 status of ETRAX_IDE? Adrian Bunk
2008-04-14 12:50 ` Mikael Starvik
2008-04-14 18:42   ` [2.6 patch] remove the broken ETRAX_IDE driver Adrian Bunk
2008-04-15 21:35     ` Bartlomiej Zolnierkiewicz [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=200804152335.21101.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=Jesper.Nilsson@axis.com \
    --cc=bunk@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    /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.