mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "Zhu, Yi" <yi.zhu@intel.com>, "Auzanneau Gregory" <mls@reolight.net>
Cc: <linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>
Subject: Re: idebus setup problem (2.6.7-rc1)
Date: Thu, 27 May 2004 17:51:04 +0200	[thread overview]
Message-ID: <200405271751.04788.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F842DB1E0@PDSMSX403.ccr.corp.intel.com>

On Thursday 27 of May 2004 17:21, Zhu, Yi wrote:
> Bartlomiej Zolnierkiewicz [B.Zolnierkiewicz@elka.pw.edu.pl] wrote:
> > I remember seeing patch related to handling '=' in kernel
> > params, maybe it's related (or maybe not).
>
> Yes, this is caused by my kernel-parameter-parsing-fix.patch.
>
> But I think below code in ide.c is a hack.
> __setup("", ide_setup);

It is a really bad hack but unfortunately it is not easy to fix.
We can only do it by introducing new kernel parameters and obsoleting
current braindamage (+ halting boot if obsolete parameter is detected).

Please note that in (very) rare corner cases current breakage can cause
data corruption.

> How about below change?

It breaks all "idex=" and "hdx=" options.
Please take a look at how ide_setup().

> --- linux-2.6.7-rc1-mm1.orig/drivers/ide/ide.c      2004-05-27
> 23:07:59.405138992 +0800
> +++ linux-2.6.7-rc1-mm1/drivers/ide/ide.c   2004-05-27
> 23:09:47.529701560 +0800
> @@ -2459,7 +2459,8 @@ void cleanup_module (void)
>
>  #else /* !MODULE */
>
> -__setup("", ide_setup);
> +__setup("hd", ide_setup);
> +__setup("ide", ide_setup);
>
>  module_init(ide_init);
>
>
> -yi


  reply	other threads:[~2004-05-27 15:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 15:21 Zhu, Yi
2004-05-27 15:51 ` Bartlomiej Zolnierkiewicz [this message]
2004-05-27 16:09 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07 11:04 Zhu, Yi
2004-06-07 23:00 ` Rusty Russell
2004-06-06 13:11 Zhu, Yi
2004-06-07  0:07 ` Rusty Russell
2004-06-03 14:05 Zhu, Yi
2004-06-03 21:31 ` Herbert Poetzl
2004-06-03 21:44   ` Bartlomiej Zolnierkiewicz
2004-06-04  4:32     ` Rusty Russell
2004-06-04 22:58       ` Bartlomiej Zolnierkiewicz
     [not found] <3ACA40606221794F80A5670F0AF15F84047998B0@PDSMSX403.ccr.corp.intel.com>
2004-05-28  4:50 ` Zhu, Yi
2004-05-28  9:11   ` Auzanneau Gregory
2004-05-28 12:50     ` Bartlomiej Zolnierkiewicz
2004-05-28 12:52       ` Auzanneau Gregory
2004-05-28 13:10         ` Bartlomiej Zolnierkiewicz
2004-05-27 16:38 Zhu, Yi
2004-06-03  6:53 ` Rusty Russell
2004-05-27 16:16 Zhu, Yi
2004-05-27 11:57 Auzanneau Gregory
2004-05-27 14:37 ` Bartlomiej Zolnierkiewicz

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=200405271751.04788.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mls@reolight.net \
    --cc=yi.zhu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®