All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Kent Gibson <warthog618@gmail.com>,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] gpiolib: Update the kernel documentation - add Return sections
Date: Tue, 9 Apr 2024 00:19:13 +0300	[thread overview]
Message-ID: <ZhRfUQP8GlJ7ZEBd@smile.fi.intel.com> (raw)
In-Reply-To: <ZhQ1l6naYpVlmlex@smile.fi.intel.com>

On Mon, Apr 08, 2024 at 09:21:11PM +0300, Andy Shevchenko wrote:
> On Fri, Apr 05, 2024 at 12:27:06AM +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.
> 
> Bart, this is the biggest part from the v1, I would like to have that applied
> first if no objections since it fixes kernel doc warnings. What do you think?

Hold on a sec, I found bigger issue that needs to be backported and this patch
needs to be rebased on top of it. I'll send an update.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2024-04-08 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 21:27 [PATCH v1 1/1] gpiolib: Update the kernel documentation - add Return sections Andy Shevchenko
2024-04-05  4:10 ` Randy Dunlap
2024-04-05  7:23   ` Dan Carpenter
2024-04-05 15:27   ` Andy Shevchenko
2024-04-05 15:33     ` Randy Dunlap
2024-04-05 15:40       ` Andy Shevchenko
2024-04-08 18:21 ` Andy Shevchenko
2024-04-08 21:19   ` Andy Shevchenko [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=ZhRfUQP8GlJ7ZEBd@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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 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.