From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: Rodrigo Freire <rfreire@redhat.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Cc: linuxwifi <linuxwifi@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iwlwifi: Document missing module options
Date: Thu, 7 Jan 2016 13:59:16 +0000 [thread overview]
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB32E983FBD@hasmsx107.ger.corp.intel.com> (raw)
In-Reply-To: 91cd61cc8ed52fab61dcf19531d821dda75db267.1452118569.git.rfreire@redhat.com
Hi,
On 01/07/2016 12:24 AM, Rodrigo Freire wrote:
> This patch documents two missing module options in the internal
> code comment block.
>
> Signed-off-by: Rodrigo Freire <rfreire@redhat.com>
> ---
> drivers/net/wireless/iwlwifi/iwl-modparams.h | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl-modparams.h b/drivers/net/wireless/iwlwifi/iwl-modparams.h
> index ac2b90d..1477277 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-modparams.h
> +++ b/drivers/net/wireless/iwlwifi/iwl-modparams.h
> @@ -102,6 +102,8 @@ enum iwl_disable_11n {
> * @power_level: power level, default = 1
> * @debug_level: levels are IWL_DL_*
> * @ant_coupling: antenna coupling in dB, default = 0
> + * @nvm_file: specifies a external NVM file
> + * @uapsd_disable: disable U-APSD, default = 1
> * @d0i3_disable: disable d0i3, default = 1,
> * @lar_disable: disable LAR (regulatory), default = 0
> * @fw_monitor: allow to use firmware monitor
Applied in our internal tree. Thanks.
prev parent reply other threads:[~2016-01-07 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 22:24 [PATCH] iwlwifi: Document missing module options Rodrigo Freire
2016-01-07 13:59 ` Grumbach, Emmanuel [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=0BA3FCBA62E2DC44AF3030971E174FB32E983FBD@hasmsx107.ger.corp.intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=rfreire@redhat.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).