From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Matt Mackall <mpm@selenic.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [PATCH] mark ide-cs broken
Date: Sun, 11 Jan 2004 22:38:30 +0000 [thread overview]
Message-ID: <20040111223830.C10920@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040111214716.GW18208@waste.org>; from mpm@selenic.com on Sun, Jan 11, 2004 at 03:47:16PM -0600
On Sun, Jan 11, 2004 at 03:47:16PM -0600, Matt Mackall wrote:
> On Sun, Jan 11, 2004 at 11:16:07AM +0000, Russell King wrote:
> > Hi,
> >
> > After receiving this bug report: http://bugme.osdl.org/show_bug.cgi?id=1457
> > and talking to Arjan, it would appear that IDECS is known to be broken.
> > Arjan has confirmed that he sees the same behaviour with his PCMCIA CDROM
> > using both 2.6 and 2.4.2x kernels.
> >
> > Therefore, I suggest that we mark it broken. The patch below is for 2.6.1
> > kernels.
>
> It's still working for me as of 2.6.0 with stock kernel and CF, so
> this is probably premature.
Ok. However, we need some way of quiescing/directing bug reports for
ide-cs with real disks to the right department (that being the IDE
department, not the PCMCIA department.)
Any better suggestions?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2004-01-11 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 11:16 [PATCH] mark ide-cs broken Russell King
2004-01-11 21:47 ` Matt Mackall
2004-01-11 22:38 ` Russell King [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=20040111223830.C10920@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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.