From: Rusty Russell <rusty@rustcorp.com.au>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Herbert Poetzl <herbert@13thfloor.at>,
"Zhu, Yi" <yi.zhu@intel.com>,
Auzanneau Gregory <mls@reolight.net>,
Jeff Garzik <jgarzik@pobox.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: idebus setup problem (2.6.7-rc1)
Date: Fri, 04 Jun 2004 14:32:43 +1000 [thread overview]
Message-ID: <1086323563.29391.1039.camel@bach> (raw)
In-Reply-To: <200406032344.19152.bzolnier@elka.pw.edu.pl>
On Fri, 2004-06-04 at 07:44, Bartlomiej Zolnierkiewicz wrote:
> On Thursday 03 of June 2004 23:31, Herbert Poetzl wrote:
> > On Thu, Jun 03, 2004 at 10:05:08PM +0800, Zhu, Yi wrote:
> > > Rusty Russell wrote:
> > > > Dislike this idea. If you have hundreds of parameters, maybe it's
> > > > supposed to be a PITA?
> > >
> > > What's your idea to make module_param support alterable param
> > > names like ide3=xxx ?
> >
> > hmm, what about making all those something like:
> >
> > ide=3:foo,bar;4:wossname
>
> We are in stable kernel and in 2.7 'idex=' and 'hdx=' will die.
Yes, and if you want to clean this up for 2.6, I'd recommend simply
putting twenty module_param_call() lines.
It's ugly, but that's because it's doing ugly things, IMHO, and I don't
think Bart would disagree?
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-06-04 4:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 14:05 idebus setup problem (2.6.7-rc1) Zhu, Yi
2004-06-03 21:31 ` Herbert Poetzl
2004-06-03 21:44 ` Bartlomiej Zolnierkiewicz
2004-06-04 4:32 ` Rusty Russell [this message]
2004-06-04 22:58 ` Bartlomiej Zolnierkiewicz
-- 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
[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 15:21 Zhu, Yi
2004-05-27 15:51 ` Bartlomiej Zolnierkiewicz
2004-05-27 16:09 ` Jeff Garzik
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=1086323563.29391.1039.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=herbert@13thfloor.at \
--cc=jgarzik@pobox.com \
--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