All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] IDE config correctness (was: Linux 2.4.21-rc4)
Date: Tue, 27 May 2003 03:37:49 +0200	[thread overview]
Message-ID: <3ED2C16D.6090904@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.55L.0305261734320.21581@freak.distro.conectiva>

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

Marcelo Tosatti wrote:
> Hi,
> 
> Here goes -rc4, hopefully fixing all problems now.
> 
> rc5 will only be released in case of REALLY bad problems.

Not really a bad problem, but CONFIG_PDC202XX_BURST should be selectable
even if CONFIG_BLK_DEV_PDC202XX_OLD=m
You decide if this goes into 2.4.21. I do not feel strongly about it.

>   o Cset exclude: c-d.hailfinger.kernel.2003@gmx.net|ChangeSet|20030526190224|33683
>   o Really fix xconfig breakage

My fix for the xconfig breakage also included this IDE config fix. When
you excluded the cset, it got lost.

Attached is the diff on top of your tree.


Regards,
Carl-Daniel

[-- Attachment #2: ide-special-udma-feature.diff --]
[-- Type: text/plain, Size: 1121 bytes --]

===== drivers/ide/Config.in 1.31 vs edited =====
--- 1.31/drivers/ide/Config.in	Mon May 26 21:38:00 2003
+++ edited/drivers/ide/Config.in	Mon May 26 23:20:49 2003
@@ -63,7 +63,7 @@
 	    dep_tristate '    NS87415 chipset support' CONFIG_BLK_DEV_NS87415 $CONFIG_BLK_DEV_IDEDMA_PCI
 	    dep_tristate '    OPTi 82C621 chipset enhanced support (EXPERIMENTAL)' CONFIG_BLK_DEV_OPTI621 $CONFIG_EXPERIMENTAL
 	    dep_tristate '    PROMISE PDC202{46|62|65|67} support' CONFIG_BLK_DEV_PDC202XX_OLD $CONFIG_BLK_DEV_IDEDMA_PCI
-	    dep_bool     '      Special UDMA Feature' CONFIG_PDC202XX_BURST $CONFIG_BLK_DEV_PDC202XX_OLD $CONFI_BLK_DEV_IDEDMA_PCI
+	    dep_mbool    '      Special UDMA Feature' CONFIG_PDC202XX_BURST $CONFIG_BLK_DEV_PDC202XX_OLD $CONFI_BLK_DEV_IDEDMA_PCI
 	    dep_tristate '    PROMISE PDC202{68|69|70|71|75|76|77} support' CONFIG_BLK_DEV_PDC202XX_NEW $CONFIG_BLK_DEV_IDEDMA_PCI
 		# FIXME - probably wants to be one for old and for new
 if [ "$CONFIG_BLK_DEV_PDC202XX_OLD" = "y" -o "$CONFIG_BLK_DEV_PDC202XX_OLD" = "m" -o "$CONFIG_BLK_DEV_PDC202XX_NEW" = "y" -o "$CONFIG_BLK_DEV_PDC202XX_NEW" = "m" ]; then

  reply	other threads:[~2003-05-27  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 20:35 Linux 2.4.21-rc4 Marcelo Tosatti
2003-05-27  1:37 ` Carl-Daniel Hailfinger [this message]
2003-05-27  3:44   ` [PATCH] IDE config correctness (was: Linux 2.4.21-rc4) Marcelo Tosatti

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=3ED2C16D.6090904@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.