From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Kalle Valo <kvalo@kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 2/2] gpiolib: Update the kernel documentation - add Return sections
Date: Tue, 9 Apr 2024 16:01:43 +0200 [thread overview]
Message-ID: <CAMRc=Mdzc2gSEX0h0Uwcxr2qMgwLLXfhJda=3AkNNYsDBQre7A@mail.gmail.com> (raw)
In-Reply-To: <ZhU57jB_pVvDz0ZR@smile.fi.intel.com>
On Tue, Apr 9, 2024 at 2:52 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Tue, Apr 09, 2024 at 02:12:51AM +0300, Andy Shevchenko wrote:
> > $ scripts/kernel-doc -v -none -Wall drivers/gpio/gpiolib* 2>&1 | grep -w warning | wc -l
> > 67
> >
> > Fix these by adding Return sections. While at it, make sure all of
> > Return sections use the same style.
>
> Since there shouldn't be hard dependency to the first one, can you consider
> applying this one, so it unblocks me?
>
I'm not sure what the resolution is for % and HTML <font> tags in the end?
Bart
next prev parent reply other threads:[~2024-04-09 14:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 23:12 [PATCH v2 0/2] gpiolib: Fix gpio_lookup_flags mess and add Return sections Andy Shevchenko
2024-04-08 23:12 ` [PATCH v2 1/2] gpiolib: Fix a mess with the GPIO_* flags Andy Shevchenko
2024-04-09 4:38 ` kernel test robot
2024-04-09 8:12 ` kernel test robot
2024-04-09 9:42 ` Bartosz Golaszewski
2024-04-09 12:51 ` Andy Shevchenko
2024-04-09 12:55 ` Bartosz Golaszewski
2024-04-09 13:30 ` Andy Shevchenko
2024-04-12 8:20 ` Linus Walleij
2024-04-12 15:25 ` Andy Shevchenko
2024-04-12 19:43 ` Bartosz Golaszewski
2024-04-16 12:22 ` Linus Walleij
2024-04-16 14:05 ` Andy Shevchenko
2024-04-16 21:07 ` Bartosz Golaszewski
2024-04-17 8:45 ` Andy Shevchenko
2024-04-17 18:39 ` Bartosz Golaszewski
2024-04-18 11:52 ` Andy Shevchenko
2024-04-19 13:29 ` Linus Walleij
2024-04-19 13:38 ` Andy Shevchenko
2024-04-08 23:12 ` [PATCH v2 2/2] gpiolib: Update the kernel documentation - add Return sections Andy Shevchenko
2024-04-09 12:51 ` Andy Shevchenko
2024-04-09 14:01 ` Bartosz Golaszewski [this message]
2024-04-09 14:06 ` Andy Shevchenko
2024-04-09 14:18 ` Bartosz Golaszewski
2024-04-09 14:29 ` Andy Shevchenko
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='CAMRc=Mdzc2gSEX0h0Uwcxr2qMgwLLXfhJda=3AkNNYsDBQre7A@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arend.vanspriel@broadcom.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=ckeepax@opensource.cirrus.com \
--cc=kvalo@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=warthog618@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).