All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the pinctrl tree
Date: Thu, 21 Apr 2022 16:12:58 +0200	[thread overview]
Message-ID: <CACRpkdYW81iLveJoNu2RDEpySqRcXWqq4XGhGFMYdLvBzhRsUw@mail.gmail.com> (raw)
In-Reply-To: <20220421171116.6dbe87cb@canb.auug.org.au>

On Thu, Apr 21, 2022 at 9:11 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the pinctrl tree, today's linux-next build (htmldocs)
> produced this warning:
>
> include/linux/gpio/driver.h:507: warning: Incorrect use of kernel-doc format:          * @of_gpio_ranges_fallback
> include/linux/gpio/driver.h:518: warning: Function parameter or member 'of_gpio_ranges_fallback' not described in 'gpio_chip'
>
> Introduced by commit
>
>   a9491df0c4ae ("gpiolib: of: Introduce hook for missing gpio-ranges")

Thanks, I just folded in a quick fix into the offending commit, a
single missing colon.

Yours,
Linus Walleij

  reply	other threads:[~2022-04-21 14:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  7:11 linux-next: build warning after merge of the pinctrl tree Stephen Rothwell
2022-04-21 14:12 ` Linus Walleij [this message]
2022-04-21 18:05   ` Stefan Wahren
  -- strict thread matches above, loose matches on Subject: below --
2021-10-27 11:01 Stephen Rothwell
2021-10-27 11:10 ` Marc Zyngier
2021-10-28  7:03   ` Mauro Carvalho Chehab
2022-01-20  3:25     ` Stephen Rothwell
2022-03-18  7:31       ` Stephen Rothwell
2022-06-05 23:33         ` Stephen Rothwell
2021-03-30  6:07 Stephen Rothwell
2021-03-30  7:51 ` Linus Walleij
2020-04-17  2:27 Stephen Rothwell
2020-04-17 10:23 ` Linus Walleij
2018-10-11  3:17 Stephen Rothwell
2018-10-11  7:51 ` Linus Walleij
2017-06-30  4:56 Stephen Rothwell
2017-06-30  4:57 ` Stephen Rothwell
2017-06-30  6:59 ` Geert Uytterhoeven
2017-06-30 13:48   ` Linus Walleij
2017-01-03  4:37 Stephen Rothwell
2015-05-20  6:40 Stephen Rothwell
2015-05-20  7:14 ` Linus Walleij
2014-05-19  6:59 Stephen Rothwell
2014-05-19  9:03 ` Maxime Ripard
2013-12-13  4:06 Stephen Rothwell

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=CACRpkdYW81iLveJoNu2RDEpySqRcXWqq4XGhGFMYdLvBzhRsUw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stefan.wahren@i2se.com \
    /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.