From: Corey Minyard <cminyard@mvista.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add boot command line parsing for the e100 driver
Date: Mon, 19 May 2003 20:30:13 -0500 [thread overview]
Message-ID: <3EC98525.80402@mvista.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0305200243380.28757-100000@mion.elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
>On Tue, 20 May 2003, Bartlomiej Zolnierkiewicz wrote:
>
>
>>On Mon, 19 May 2003, Corey Minyard wrote:
>>
>>
>>
>>>Jeff Garzik wrote:
>>>
>>>
>>>
>>>>>instead of adding such horrible cruft Corey did it should just use the
>>>>>proper API.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>An API already exists, and it is source compatible between 2.4 and 2.5:
>>>>ethX=.... on the kernel command line.
>>>>
>>>>The proper patch would pick up options from there.
>>>>
>>>>
>>>>
>>>Can you tell me where this is? I found the "ether=xxx" and
>>>"netdev=xxx", but they are not suitible. I also could not find
>>>"module_parame" anywhere on google or in the kernel.
>>>
>>>-Corey
>>>
>>>
>>:-) module_parm(), look at include/linux/moduleparam.h
>>and scsi for usage examples
>>
>>
>
>ugh. s/module_parm/module_param/
>
Thank you. Nobody seems to be able to type correctly today :-). I had
actually found it, and looked it over. It looks pretty nice, although
the lack of documentation is somewhat annoying.
However, if the ethX=.... exists, I would far prefer to use that. (The
parameters for what am doing have to be at bootup to work, it can't be
after the fact. I hunted for a while, and I still couldn't find it,
btw.) Otherwise, it's really up to the driver maintainers. I will
adjust as they want, I will use the module_param stuff or the old
__setup stuff. I would like to get this in, though.
-Corey
prev parent reply other threads:[~2003-05-20 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 16:09 [PATCH] Add boot command line parsing for the e100 driver Corey Minyard
2003-05-19 16:17 ` Christoph Hellwig
2003-05-19 16:30 ` Jeff Garzik
2003-05-19 16:33 ` Christoph Hellwig
2003-05-19 16:40 ` Jeff Garzik
2003-05-19 17:04 ` Corey Minyard
2003-05-20 0:16 ` Bartlomiej Zolnierkiewicz
2003-05-20 0:44 ` Bartlomiej Zolnierkiewicz
2003-05-20 1:30 ` Corey Minyard [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=3EC98525.80402@mvista.com \
--to=cminyard@mvista.com \
--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