From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: kerneldoc fixes for excess members
Date: Mon, 2 Sep 2024 14:10:37 +0200 [thread overview]
Message-ID: <b67efbc8-ff21-486b-9961-498eae0f85bf@linaro.org> (raw)
In-Reply-To: <CAMRc=McgbL5DCu2mr6oWERMQMFQU1Bm-1BkC+XR=-2fPXpOW4A@mail.gmail.com>
On 02/09/2024 14:03, Bartosz Golaszewski wrote:
> On Mon, Aug 26, 2024 at 6:18 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> 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'
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>
> I have a different patch in my queue that addresses the syscon warning
> already. Can you resend just the pch part?
Heh, you just picked up something which was sent week after mine. :/
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-02 12:10 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
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 [this message]
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=b67efbc8-ff21-486b-9961-498eae0f85bf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--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