mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	linux-kernel@vger.kernel.org
Cc: Colin Ian King <colin.king@canonical.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] firmware_loader: Fix a typo ("syfs" -> "sysfs")
Date: Tue, 30 Apr 2019 20:44:17 +0530	[thread overview]
Message-ID: <a87e799e-73d3-6971-2df5-59ba34fb1446@codeaurora.org> (raw)
In-Reply-To: <20190430145610.1291-1-j.neuschaefer@gmx.net>


On 4/30/2019 8:26 PM, Jonathan Neuschäfer wrote:
> "sysfs" was misspelled in a comment and a log message.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>

Cheers,
-Mukesh
> ---
>   drivers/base/firmware_loader/fallback.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/firmware_loader/fallback.c b/drivers/base/firmware_loader/fallback.c
> index b5c865fe263b..f962488546b6 100644
> --- a/drivers/base/firmware_loader/fallback.c
> +++ b/drivers/base/firmware_loader/fallback.c
> @@ -674,8 +674,8 @@ static bool fw_run_sysfs_fallback(enum fw_opt opt_flags)
>    *
>    * This function is called if direct lookup for the firmware failed, it enables
>    * a fallback mechanism through userspace by exposing a sysfs loading
> - * interface. Userspace is in charge of loading the firmware through the syfs
> - * loading interface. This syfs fallback mechanism may be disabled completely
> + * interface. Userspace is in charge of loading the firmware through the sysfs
> + * loading interface. This sysfs fallback mechanism may be disabled completely
>    * on a system by setting the proc sysctl value ignore_sysfs_fallback to true.
>    * If this false we check if the internal API caller set the @FW_OPT_NOFALLBACK
>    * flag, if so it would also disable the fallback mechanism. A system may want
> @@ -693,7 +693,7 @@ int firmware_fallback_sysfs(struct firmware *fw, const char *name,
>   		return ret;
>
>   	if (!(opt_flags & FW_OPT_NO_WARN))
> -		dev_warn(device, "Falling back to syfs fallback for: %s\n",
> +		dev_warn(device, "Falling back to sysfs fallback for: %s\n",
>   				 name);
>   	else
>   		dev_dbg(device, "Falling back to sysfs fallback for: %s\n",
> --
> 2.20.1
>

      reply	other threads:[~2019-04-30 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 14:56 Jonathan Neuschäfer
2019-04-30 15:14 ` Mukesh Ojha [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=a87e799e-73d3-6971-2df5-59ba34fb1446@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=colin.king@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rafael@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

Powered by JetHome