From: Philipp Stanner <pstanner@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
pstanner@redhat.com
Subject: Re: [PATCH v2 2/2] devres: Don't use "proxy" headers
Date: Thu, 29 Feb 2024 21:21:43 +0100 [thread overview]
Message-ID: <d9b2ce52569b2c6a745ca3efa678fa83adfe0fac.camel@redhat.com> (raw)
In-Reply-To: <20240229155507.3853059-3-andriy.shevchenko@linux.intel.com>
Wait a second..
On Thu, 2024-02-29 at 17:53 +0200, Andy Shevchenko wrote:
> Update header inclusions to follow IWYU (Include What You Use)
> principle.
Hm, what tree is this based on?
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> lib/devres.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/lib/devres.c b/lib/devres.c
> index 27f280a39dca..4fc152de6d8b 100644
> --- a/lib/devres.c
> +++ b/lib/devres.c
> @@ -1,10 +1,13 @@
> // SPDX-License-Identifier: GPL-2.0
> +#include <linux/bug.h>
> #include <linux/device.h>
Where does device.h come from?
That's not on master, is it? (see below).
Is this based on my PCI-devres series?
> -#include <linux/err.h>
> -#include <linux/io.h>
> -#include <linux/gfp.h>
> +#include <linux/errno.h>
> #include <linux/export.h>
> +#include <linux/gfp_types.h>
> +#include <linux/io.h>
> +#include <linux/ioport.h>
> #include <linux/of_address.h>
> +#include <linux/types.h>
>
> enum devm_ioremap_type {
> DEVM_IOREMAP = 0,
That's what's currently in Linus's master:
// SPDX-License-Identifier: GPL-2.0
#include <linux/err.h>
#include <linux/pci.h>
#include <linux/io.h>
#include <linux/gfp.h>
#include <linux/export.h>
#include <linux/of_address.h>
enum devm_ioremap_type {
P.
next prev parent reply other threads:[~2024-02-29 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 15:53 [PATCH v2 0/2] devres: A couple of cleanups Andy Shevchenko
2024-02-29 15:53 ` [PATCH v2 1/2] devres: Switch to use dev_err_probe() for unification Andy Shevchenko
2024-02-29 20:11 ` Philipp Stanner
2024-02-29 15:53 ` [PATCH v2 2/2] devres: Don't use "proxy" headers Andy Shevchenko
2024-02-29 20:21 ` Philipp Stanner [this message]
2024-02-29 20:50 ` Andy Shevchenko
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=d9b2ce52569b2c6a745ca3efa678fa83adfe0fac.camel@redhat.com \
--to=pstanner@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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®