Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: kerneldoc fixes for excess members
Date: Mon, 26 Aug 2024 20:25:57 +0300	[thread overview]
Message-ID: <Zsy6pZ9LYDk0LOHs@smile.fi.intel.com> (raw)
In-Reply-To: <20240826161850.74447-1-krzysztof.kozlowski@linaro.org>

On Mon, Aug 26, 2024 at 06:18:50PM +0200, Krzysztof Kozlowski wrote:
> Drop kerneldoc descriptions of struct members which do not exist to fix
> W=1 warnings:
> 
>   drivers/gpio/gpio-pch.c:101: warning: Excess struct member 'lock' description in 'pch_gpio'
>   drivers/gpio/gpio-syscon.c:46: warning: Excess struct member 'compatible' description in 'syscon_gpio_data'

I prefer on per-driver basis, but since it's simple and I have nothing
in my queue,

Reviewed-by: Andy Shevchenko <andy@kernel.org> # for gpio-pch

in the assumption that Bart takes it directly.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-08-26 17:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 16:18 [PATCH] gpio: kerneldoc fixes for excess members Krzysztof Kozlowski
2024-08-26 17:25 ` Andy Shevchenko [this message]
2024-08-27 13:55   ` Krzysztof Kozlowski
2024-08-27 14:01     ` Andy Shevchenko
2024-09-02 10:09       ` Bartosz Golaszewski
2024-09-02 10:37         ` Andy Shevchenko
2024-09-02 12:02           ` Bartosz Golaszewski
2024-09-02 12:03 ` Bartosz Golaszewski
2024-09-02 12:06   ` Krzysztof Kozlowski
2024-09-02 12:10   ` Krzysztof Kozlowski
2024-09-02 12:17     ` Andy Shevchenko
2024-09-02 12:34     ` Bartosz Golaszewski

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=Zsy6pZ9LYDk0LOHs@smile.fi.intel.com \
    --to=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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