public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: [PATCH] mark ide-cs broken
Date: Sun, 11 Jan 2004 11:16:07 +0000	[thread overview]
Message-ID: <20040111111607.A1931@flint.arm.linux.org.uk> (raw)

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.

If anyone wants to know the details of why it's broken, please don't mail
me - I don't know - the best I can do is refer you to the above URL.

As far as bug 1457 goes - I'll reassign it to "Drivers - Other" later today
since we don't have an IDE component in bugme.

--- orig/drivers/ide/Kconfig	Fri Jan  9 22:39:21 2004
+++ linux/drivers/ide/Kconfig	Sun Jan 11 11:00:11 2004
@@ -173,7 +173,7 @@
 
 config BLK_DEV_IDECS
 	tristate "PCMCIA IDE support"
-	depends on PCMCIA
+	depends on PCMCIA && BROKEN
 	help
 	  Support for outboard IDE disks, tape drives, and CD-ROM drives
 	  connected through a  PCMCIA card.

-- 
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

             reply	other threads:[~2004-01-11 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 11:16 Russell King [this message]
2004-01-11 21:47 ` [PATCH] mark ide-cs broken Matt Mackall
2004-01-11 22:38   ` Russell King

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=20040111111607.A1931@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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox