devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Rob Herring'" <robh@kernel.org>,
	"'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] soc: samsung: Explicitly include correct DT includes
Date: Mon, 17 Jul 2023 17:07:53 +0530	[thread overview]
Message-ID: <001d01d9b8a3$20bd7ed0$62387c70$@samsung.com> (raw)
In-Reply-To: <20230714175147.4068046-1-robh@kernel.org>



> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Friday, July 14, 2023 11:22 PM
> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; Alim Akhtar
> <alim.akhtar@samsung.com>
> Cc: devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
linux-
> samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] soc: samsung: Explicitly include correct DT includes
> 
> 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.
> 
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---

Acked-by: Alim Akhtar <alim.akhtar@samsung.com>

>  drivers/soc/samsung/exynos-chipid.c | 1 -
>  drivers/soc/samsung/exynos-pmu.c    | 2 +-
>  drivers/soc/samsung/pm_domains.c    | 3 ++-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/soc/samsung/exynos-chipid.c
b/drivers/soc/samsung/exynos-
> chipid.c
> index 0fb3631e7346..7ba45c4aff97 100644
> --- a/drivers/soc/samsung/exynos-chipid.c
> +++ b/drivers/soc/samsung/exynos-chipid.c
> @@ -17,7 +17,6 @@
>  #include <linux/mfd/syscon.h>
>  #include <linux/module.h>
>  #include <linux/of.h>
> -#include <linux/of_device.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>
>  #include <linux/slab.h>
> diff --git a/drivers/soc/samsung/exynos-pmu.c
b/drivers/soc/samsung/exynos-
> pmu.c
> index 5b2664da9853..250537d7cfd6 100644
> --- a/drivers/soc/samsung/exynos-pmu.c
> +++ b/drivers/soc/samsung/exynos-pmu.c
> @@ -7,9 +7,9 @@
> 
>  #include <linux/of.h>
>  #include <linux/of_address.h>
> -#include <linux/of_device.h>
>  #include <linux/mfd/core.h>
>  #include <linux/mfd/syscon.h>
> +#include <linux/of_platform.h>
>  #include <linux/platform_device.h>
>  #include <linux/delay.h>
> 
> diff --git a/drivers/soc/samsung/pm_domains.c
> b/drivers/soc/samsung/pm_domains.c
> index d07f3c9d6903..9b502e8751d1 100644
> --- a/drivers/soc/samsung/pm_domains.c
> +++ b/drivers/soc/samsung/pm_domains.c
> @@ -11,11 +11,12 @@
> 
>  #include <linux/io.h>
>  #include <linux/err.h>
> +#include <linux/platform_device.h>
>  #include <linux/slab.h>
>  #include <linux/pm_domain.h>
>  #include <linux/delay.h>
> +#include <linux/of.h>
>  #include <linux/of_address.h>
> -#include <linux/of_platform.h>
>  #include <linux/pm_runtime.h>
> 
>  struct exynos_pm_domain_config {
> --
> 2.40.1



  reply	other threads:[~2023-07-17 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230714175226epcas5p2957137e6e0b4a69efb913fe744be827a@epcas5p2.samsung.com>
2023-07-14 17:51 ` [PATCH] soc: samsung: Explicitly include correct DT includes Rob Herring
2023-07-17 11:37   ` Alim Akhtar [this message]
2023-07-20  9:32   ` Krzysztof Kozlowski

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='001d01d9b8a3$20bd7ed0$62387c70$@samsung.com' \
    --to=alim.akhtar@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@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;
as well as URLs for NNTP newsgroup(s).