From: Randy Dunlap <rdunlap@xenotime.net>
To: David Miller <davem@davemloft.net>
Cc: brian.haley@hp.com, greg@enjellic.com, nhorman@tuxdriver.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] IPv6: Update documentation for better built-in help with params
Date: Mon, 25 Jan 2010 13:43:01 -0800 [thread overview]
Message-ID: <20100125134301.e4849520.rdunlap@xenotime.net> (raw)
In-Reply-To: <20100125.133411.191160829.davem@davemloft.net>
On Mon, 25 Jan 2010 13:34:11 -0800 (PST) David Miller wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
> Date: Mon, 25 Jan 2010 13:31:33 -0800
>
> > On Mon, 25 Jan 2010 13:21:42 -0800 (PST) David Miller wrote:
> >
> >> From: Brian Haley <brian.haley@hp.com>
> >> Date: Mon, 25 Jan 2010 12:28:15 -0500
> >>
> >> > I guess Documentation/kernel-parameters.txt is where such things
> >> > live, can I send you a patch for that or does it need to go
> >> > through someone else?
> >>
> >> I think lkml is a suitable place to submit something like
> >> that.
> >> --
> >
> > Sure, but if it's networking parameters, you (David) could still merge it...
>
> It's not about networking parameters.
OK, I didn't see the patch itself, sorry.
> It's about adding a generic mention somewhere central that you can set
> "module parameters" on the kernel command line when a module is built
> statically into the kernel.
Maybe like this, from that same file:
Module parameters for modules that are built into the kernel image
are specified on the kernel command line with the module name plus
'.' plus parameter name, with '=' and value if appropriate, such as:
usbcore.blinkenlights=1
I'll search for the patch...
---
~Randy
prev parent reply other threads:[~2010-01-25 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 19:01 Global IPV6 auto-configuration does not work as expected greg
2010-01-22 20:24 ` [PATCH] IPv6: Update documentation for better built-in help with params Brian Haley
2010-01-23 2:32 ` David Miller
2010-01-25 17:28 ` Brian Haley
2010-01-25 21:21 ` David Miller
2010-01-25 21:31 ` Randy Dunlap
2010-01-25 21:34 ` David Miller
2010-01-25 21:43 ` Randy Dunlap [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=20100125134301.e4849520.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=greg@enjellic.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).