From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: fix spelling mistake "capabilites" -> "capabilities"
Date: Tue, 16 Apr 2019 12:24:16 +0530 [thread overview]
Message-ID: <520f6626-246b-005f-53ef-df2f75a89cd9@codeaurora.org> (raw)
In-Reply-To: <20190415125204.7386-1-colin.king@canonical.com>
On 4/15/2019 6:22 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a module parameter description. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/platform/x86/thinkpad_acpi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c
> index 57d9ae9d8e56..9192b686e9a6 100644
> --- a/drivers/platform/x86/thinkpad_acpi.c
> +++ b/drivers/platform/x86/thinkpad_acpi.c
> @@ -10269,7 +10269,7 @@ MODULE_PARM_DESC(volume_mode,
>
> module_param_named(volume_capabilities, volume_capabilities, uint, 0444);
> MODULE_PARM_DESC(volume_capabilities,
> - "Selects the mixer capabilites: 0=auto, 1=volume and mute, 2=mute only");
> + "Selects the mixer capabilities: 0=auto, 1=volume and mute, 2=mute only");
>
> module_param_named(volume_control, volume_control_allowed, bool, 0444);
> MODULE_PARM_DESC(volume_control,
next prev parent reply other threads:[~2019-04-16 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 12:52 [PATCH] platform/x86: thinkpad_acpi: fix spelling mistake "capabilites" -> "capabilities" Colin King
2019-04-16 6:54 ` Mukesh Ojha [this message]
2019-05-06 8:49 ` Andy Shevchenko
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=520f6626-246b-005f-53ef-df2f75a89cd9@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=andy@infradead.org \
--cc=colin.king@canonical.com \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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