linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Guinot <simon.guinot@sequanux.org>
To: Nick Bowler <nbowler@draconx.ca>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: Fix gpio-f7188x module name in Kconfig help text.
Date: Wed, 25 Mar 2020 13:12:05 +0100	[thread overview]
Message-ID: <20200325121205.GT21102@kw.sim.vm.gnt> (raw)
In-Reply-To: <20200325005707.5891-1-nbowler@draconx.ca>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On Tue, Mar 24, 2020 at 08:57:07PM -0400, Nick Bowler wrote:
> The Kconfig help text for the gpio-f7188x driver says that if you
> compile the driver as a module, the module will be called f7188x-gpio.
> This is a lie: the module is called gpio-f7188x.

And what about just a mistake ? :)

Acked-by: Simon Guinot <simon.guinot@sequanux.org>

> 
> Change the help text to be consistent with reality.
> 
> Signed-off-by: Nick Bowler <nbowler@draconx.ca>
> ---
>  drivers/gpio/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index b8013cf90064..8cf91a9fbd18 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -755,7 +755,7 @@ config GPIO_F7188X
>  	  chips F71869, F71869A, F71882FG, F71889F and F81866.
>  
>  	  To compile this driver as a module, choose M here: the module will
> -	  be called f7188x-gpio.
> +	  be called gpio-f7188x.
>  
>  config GPIO_GPIO_MM
>  	tristate "Diamond Systems GPIO-MM GPIO support"
> -- 
> 2.24.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-03-25 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  0:57 [PATCH] gpio: Fix gpio-f7188x module name in Kconfig help text Nick Bowler
2020-03-25 12:12 ` Simon Guinot [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=20200325121205.GT21102@kw.sim.vm.gnt \
    --to=simon.guinot@sequanux.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@draconx.ca \
    /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).