All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Rob Herring <robh@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: Kconfig: Correct typo in NVMEM_RMEM
Date: Wed, 3 Feb 2021 16:36:29 +0000	[thread overview]
Message-ID: <ac9794b4-1e34-c3a0-ef33-4271bcce3fdc@linaro.org> (raw)
In-Reply-To: <20210203102932.7277-1-nsaenzjulienne@suse.de>



On 03/02/2021 10:29, Nicolas Saenz Julienne wrote:
> s/drivers/driver/ as the configuration selects a single driver.
> 
> Fixes: 2bf4fd065384 ("nvmem: Add driver to expose reserved memory as nvmem")
> Suggested-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> ---
>   drivers/nvmem/Kconfig | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied thanks!

--srini


> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index fecc19b884bf..75d2594c16e1 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -273,7 +273,7 @@ config SPRD_EFUSE
>   config NVMEM_RMEM
>   	tristate "Reserved Memory Based Driver Support"
>   	help
> -	  This drivers maps reserved memory into an nvmem device. It might be
> +	  This driver maps reserved memory into an nvmem device. It might be
>   	  useful to expose information left by firmware in memory.
>   
>   	  This driver can also be built as a module. If so, the module
> 

      parent reply	other threads:[~2021-02-03 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 10:29 [PATCH] nvmem: Kconfig: Correct typo in NVMEM_RMEM Nicolas Saenz Julienne
2021-02-03 16:34 ` Randy Dunlap
2021-02-03 16:36 ` Srinivas Kandagatla [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=ac9794b4-1e34-c3a0-ef33-4271bcce3fdc@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=rdunlap@infradead.org \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.