From: Eddie James <eajames@linux.ibm.com>
To: Rob Herring <robh@kernel.org>, Jeremy Kerr <jk@ozlabs.org>,
Joel Stanley <joel@jms.id.au>,
Alistar Popple <alistair@popple.id.au>
Cc: linux-fsi@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fsi: Explicitly include correct DT includes
Date: Tue, 18 Jul 2023 16:57:39 -0500 [thread overview]
Message-ID: <9b4102fc-b630-8463-aa00-e7d8aab4a2be@linux.ibm.com> (raw)
In-Reply-To: <20230718205508.1790932-1-robh@kernel.org>
On 7/18/23 15:55, Rob Herring wrote:
> The DT of_device.h and of_platform.h date back to the separate
> of_platform_bus_type before it as merged into the regular platform bus.
> As part of that merge prepping Arm DT support 13 years ago, they
> "temporarily" include each other. They also include platform_device.h
> and of.h. As a result, there's a pretty much random mix of those include
> files used throughout the tree. In order to detangle these headers and
> replace the implicit includes with struct declarations, users need to
> explicitly include the correct includes.
Thanks,
Reviewed-by: Eddie James <eajames@linux.ibm.com>
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> v2:
> - I inadvertently had a dependency in my tree partially updating the
> headers. That's squashed in now.
> ---
> drivers/fsi/fsi-occ.c | 2 +-
> drivers/fsi/fsi-sbefifo.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/fsi/fsi-occ.c b/drivers/fsi/fsi-occ.c
> index abdd37d5507f..da35ca9e84a6 100644
> --- a/drivers/fsi/fsi-occ.c
> +++ b/drivers/fsi/fsi-occ.c
> @@ -15,7 +15,7 @@
> #include <linux/mutex.h>
> #include <linux/fsi-occ.h>
> #include <linux/of.h>
> -#include <linux/of_device.h>
> +#include <linux/of_platform.h>
> #include <linux/platform_device.h>
> #include <linux/sched.h>
> #include <linux/slab.h>
> diff --git a/drivers/fsi/fsi-sbefifo.c b/drivers/fsi/fsi-sbefifo.c
> index 9912b7a6a4b9..4bae52c98620 100644
> --- a/drivers/fsi/fsi-sbefifo.c
> +++ b/drivers/fsi/fsi-sbefifo.c
> @@ -22,8 +22,8 @@
> #include <linux/module.h>
> #include <linux/mutex.h>
> #include <linux/of.h>
> -#include <linux/of_device.h>
> #include <linux/of_platform.h>
> +#include <linux/platform_device.h>
> #include <linux/sched.h>
> #include <linux/slab.h>
> #include <linux/uaccess.h>
prev parent reply other threads:[~2023-07-18 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 20:55 Rob Herring
2023-07-18 21:57 ` Eddie James [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=9b4102fc-b630-8463-aa00-e7d8aab4a2be@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
Powered by JetHome