linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: renesas: rza1: Fix kerneldoc function names
Date: Tue, 19 Oct 2021 14:54:39 +0200	[thread overview]
Message-ID: <CAMuHMdX6OO19+pgxUYATT9AZ5BuXXMzRCPbtn7aZC_Lc6pt96g@mail.gmail.com> (raw)
In-Reply-To: <20211019124315.5dg5pfaas2qmm7lx@uno.localdomain>

Hi Jacopo,

On Tue, Oct 19, 2021 at 2:42 PM Jacopo Mondi <jacopo@jmondi.org> wrote:
> On Tue, Oct 19, 2021 at 02:34:22PM +0200, Geert Uytterhoeven wrote:
> > make W=1:
> >
> >     drivers/pinctrl/renesas/pinctrl-rza1.c:770: warning: expecting prototype for rza1_gpio_disable_free(). Prototype was for rza1_gpio_free() instead
> >     drivers/pinctrl/renesas/pinctrl-rza1.c:889: warning: expecting prototype for rza1_parse_pmx_function(). Prototype was for rza1_parse_pinmux_node() instead
> >
> > Fixes: 5a49b644b3075f88 ("pinctrl: Renesas RZ/A1 pin and gpio controller")
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Thanks, looking at the driver now it seems I was really eager to write
> comments at the time I wrote it! :)
>
> Probably all kernel-doc comments should be demoted to regular
> comments, as they're only internal driver functions.

;-)

> > --- a/drivers/pinctrl/renesas/pinctrl-rza1.c
> > +++ b/drivers/pinctrl/renesas/pinctrl-rza1.c
> > @@ -757,7 +757,7 @@ static int rza1_gpio_request(struct gpio_chip *chip, unsigned int gpio)
> >  }
> >
> >  /**
> > - * rza1_gpio_disable_free() - reset a pin
> > + * rza1_gpio_free() - reset a pin
> >   *
> >   * Surprisingly, disable_free a gpio, is equivalent to request it.
>
> s/disable_free/free ?

Yup, will fix while applying to:

    disabling a gpio is equivalent to requesting it

> Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-10-19 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 12:34 [PATCH] pinctrl: renesas: rza1: Fix kerneldoc function names Geert Uytterhoeven
2021-10-19 12:43 ` Jacopo Mondi
2021-10-19 12:54   ` Geert Uytterhoeven [this message]
2021-10-26  7:35     ` Geert Uytterhoeven

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=CAMuHMdX6OO19+pgxUYATT9AZ5BuXXMzRCPbtn7aZC_Lc6pt96g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo@jmondi.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).