Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 16EA8608CC
Subject: Re: [PATCH] firmware_loader: Fix a typo ("syfs" -> "sysfs")
To:     =?UTF-8?Q?Jonathan_Neusch=c3=a4fer?= <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>
References: <20190430145610.1291-1-j.neuschaefer@gmx.net>
From:   Mukesh Ojha <mojha@codeaurora.org>
Message-ID: <a87e799e-73d3-6971-2df5-59ba34fb1446@codeaurora.org>
Date:   Tue, 30 Apr 2019 20:44:17 +0530
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190430145610.1291-1-j.neuschaefer@gmx.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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
>