From: Pavel Machek <pavel@ucw.cz>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Duje Mihanović" <duje.mihanovic@skole.hr>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lee Jones" <lee@kernel.org>
Subject: Re: [PATCH v2 1/1] leds: expresswire: Don't use "proxy" headers
Date: Fri, 23 Feb 2024 21:56:56 +0100 [thread overview]
Message-ID: <ZdkGmE2HFxXpIonR@duo.ucw.cz> (raw)
In-Reply-To: <20240223203010.881065-1-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hi!
> Update header inclusions to follow IWYU (Include What You Use)
> principle.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2: added one more missing header
> drivers/leds/leds-expresswire.c | 4 ++++
> include/linux/leds-expresswire.h | 4 +++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/leds-expresswire.h b/include/linux/leds-expresswire.h
> index 3c61902ccac8..a422921f4159 100644
> --- a/include/linux/leds-expresswire.h
> +++ b/include/linux/leds-expresswire.h
> @@ -8,7 +8,9 @@
> #ifndef _LEDS_EXPRESSWIRE_H
> #define _LEDS_EXPRESSWIRE_H
>
> -#include <linux/gpio/consumer.h>
> +#include <linux/types.h>
> +
> +struct gpio_desc;
If include tweak means you need to declare struct, is it ian
improvement?
BR,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-02-23 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:30 [PATCH v2 1/1] leds: expresswire: Don't use "proxy" headers Andy Shevchenko
2024-02-23 20:56 ` Pavel Machek [this message]
2024-02-24 15:31 ` Duje Mihanović
2024-02-26 14:27 ` Andy Shevchenko
2024-02-26 14:34 ` Andy Shevchenko
2024-02-24 16:02 ` Duje Mihanović
2024-02-26 14:34 ` Andy Shevchenko
2024-02-29 17:22 ` (subset) " Lee Jones
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=ZdkGmE2HFxXpIonR@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=andriy.shevchenko@linux.intel.com \
--cc=duje.mihanovic@skole.hr \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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