From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Clausen <andrew.p.clausen@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rfkill: parameters documentation
Date: Mon, 05 Jan 2015 10:24:44 +0100 [thread overview]
Message-ID: <1420449884.1898.3.camel@sipsolutions.net> (raw)
In-Reply-To: <CAAXZBWLOKL8Uu9No_tQga34nFurmeK2HP9qixO1jCXw1Y0t5HA@mail.gmail.com> (sfid-20150102_200110_665438_46A7C2C9)
On Fri, 2015-01-02 at 19:01 +0000, Andrew Clausen wrote:
> Hi all,
>
> This patch documents two rfkill module parameters, namely
> rfkill.default_state and rfkill.master_switch_mode.
>
> I constructed the patch from Ubuntu packaged source, but I'm happy to
> adapt it to any git tree.
>
> Kind regards,
> Andrew
>
> Signed-off-by: Andrew Clausen <andrew.p.clausen@gmail.com>
Looks fine to me (though the commit message shouldn't contain the email
"boilerplate" of "hi all" etc - should just be
rfkill: document module parameters
Document the two rfkill module parameters "default_state" and
"master_switch_mode".
Signed-off-by: ...
However I'm not sure I should apply this through my tree?
johannes
> ---
>
> diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> index 011855b..824ee3b 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2999,6 +2999,20 @@ bytes respectively. Such letter suffixes can
> also be entirely omitted.
>
> retain_initrd [RAM] Keep initrd memory after extraction
>
> + rfkill.default_state=
> + 0 "airplane mode". All wifi, bluetooth, wimax,
> + gps, fm, etc. communication is blocked by
> + default.
> + 1 Unblocked.
> +
> + rfkill.master_switch_mode=
> + 0 The "airplane mode" button does nothing.
> + 1 The "airplane mode" button toggles between
> + everything blocked and the previous
> + configuration.
> + 2 The "airplane mode" button toggles between
> + everything blocked and everything unblocked.
> +
> rhash_entries= [KNL,NET]
> Set number of hash buckets for route cache
>
> diff --git a/Documentation/rfkill.txt b/Documentation/rfkill.txt
> index 427e897..2ee6ef9 100644
> --- a/Documentation/rfkill.txt
> +++ b/Documentation/rfkill.txt
> @@ -25,6 +25,9 @@ whether they can be changed or not:
> - soft block: writable radio block (need not be readable) that is set by
> the system software.
>
> +The rfkill subsystem has two parameters, rfkill.default_state and
> +rfkill.master_switch_mode, which are documented in kernel-parameters.txt.
> +
>
> 2. Implementation details
>
next prev parent reply other threads:[~2015-01-05 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 19:01 [PATCH] rfkill: parameters documentation Andrew Clausen
2015-01-05 9:24 ` Johannes Berg [this message]
2015-01-05 10:03 ` Andrew Clausen
2015-01-06 10:10 ` Johannes Berg
2015-01-09 22:21 ` Johannes Berg
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=1420449884.1898.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=andrew.p.clausen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@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).