From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: 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 12:28:15 -0500 [thread overview]
Message-ID: <4B5DD4AF.8050800@hp.com> (raw)
In-Reply-To: <20100122.183223.197255353.davem@davemloft.net>
David Miller wrote:
> From: Brian Haley <brian.haley@hp.com>
> Date: Fri, 22 Jan 2010 15:24:49 -0500
>
>> Update IPv6 documentation to describe how to set parameters when it's
>> built-into the kernel. Reported by <greg@enjellic.com>.
>>
>> Signed-off-by: Brian Haley <brian.haley@hp.com>
>
> So are you going to also add a mention of this fact to every single
> place in the documentation that talks about some arbitrary module
> option?
>
> That doesn't make any sense, and neither does this patch.
>
> It's better to make it more apparent that module options can
> be set on the kernel command line when something is compiled
> statically into the kernel.
>
> That way it only needs to be explained in one place, not in
> several.
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?
-Brian
next prev parent reply other threads:[~2010-01-25 17:28 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 [this message]
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
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=4B5DD4AF.8050800@hp.com \
--to=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).