From: Guenter Roeck <linux@roeck-us.net>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
James Hilliard <james.hilliard1@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH v3 2/2] watchdog: Don't use "proxy" headers
Date: Wed, 16 Jul 2025 17:25:08 -0700 [thread overview]
Message-ID: <c38edb68-e250-4c54-8a91-e678d3f1eae9@roeck-us.net> (raw)
In-Reply-To: <20250708133646.70384-3-andriy.shevchenko@linux.intel.com>
On 7/8/25 06:33, Andy Shevchenko wrote:
> Update header inclusions to follow IWYU (Include What You Use)
> principle.
>
> Note that kernel.h is discouraged to be included as it's written
> at the top of that file.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/watchdog_core.h | 8 +++++++-
> drivers/watchdog/watchdog_pretimeout.c | 2 ++
> include/linux/watchdog.h | 12 ++++++++----
> 3 files changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/watchdog/watchdog_core.h b/drivers/watchdog/watchdog_core.h
> index 5b35a8439e26..ab825d9f9248 100644
> --- a/drivers/watchdog/watchdog_core.h
> +++ b/drivers/watchdog/watchdog_core.h
> @@ -24,8 +24,14 @@
> * This material is provided "AS-IS" and at no charge.
> */
>
> -#include <linux/hrtimer.h>
> +#include <linux/cdev.h>
> +#include <linux/device.h>
> +#include <linux/hrtimer_types.h>
> +#include <linux/init.h>
> #include <linux/kthread.h>
> +#include <linux/mutex_types.h>
> +#include <linux/types.h>
> +#include <linux/watchdog.h>
>
> #define MAX_DOGS 32 /* Maximum number of watchdog devices */
>
> diff --git a/drivers/watchdog/watchdog_pretimeout.c b/drivers/watchdog/watchdog_pretimeout.c
> index e5295c990fa1..2526436dc74d 100644
> --- a/drivers/watchdog/watchdog_pretimeout.c
> +++ b/drivers/watchdog/watchdog_pretimeout.c
> @@ -7,6 +7,8 @@
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> #include <linux/string.h>
> +#include <linux/sysfs.h>
> +#include <linux/types.h>
> #include <linux/watchdog.h>
>
> #include "watchdog_core.h"
> diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
> index 99660197a36c..8c60687a3e55 100644
> --- a/include/linux/watchdog.h
> +++ b/include/linux/watchdog.h
> @@ -9,14 +9,18 @@
> #ifndef _LINUX_WATCHDOG_H
> #define _LINUX_WATCHDOG_H
>
> -
> #include <linux/bitops.h>
> -#include <linux/cdev.h>
> -#include <linux/device.h>
> -#include <linux/kernel.h>
> +#include <linux/limits.h>
> #include <linux/notifier.h>
> +#include <linux/printk.h>
> +#include <linux/types.h>
> +
> #include <uapi/linux/watchdog.h>
>
> +struct attribute_group;
> +struct device;
> +struct module;
> +
> struct watchdog_ops;
> struct watchdog_device;
> struct watchdog_core_data;
prev parent reply other threads:[~2025-07-17 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 13:33 [PATCH v3 0/2] watchdog: Don't use "proxy" inclusions Andy Shevchenko
2025-07-08 13:33 ` [PATCH v3 1/2] watchdog: it87_wdt: Don't use "proxy" headers Andy Shevchenko
2025-07-17 0:24 ` Guenter Roeck
2025-07-08 13:33 ` [PATCH v3 2/2] watchdog: " Andy Shevchenko
2025-07-17 0:25 ` Guenter Roeck [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=c38edb68-e250-4c54-8a91-e678d3f1eae9@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=james.hilliard1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®