public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Jernej Škrabec <jernej.skrabec@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 21/23] soc: sunxi: Explicitly include correct DT includes
Date: Sun, 06 Aug 2023 13:41:53 +0200	[thread overview]
Message-ID: <5696647.DvuYhMxLoT@jernej-laptop> (raw)
In-Reply-To: <20230803-dt-header-cleanups-for-soc-v2-21-d8de2cc88bff@kernel.org>

Dne petek, 04. avgust 2023 ob 00:43:01 CEST je Rob Herring napisal(a):
> 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>

Applied to sunxi tree, thanks!

Best regards,
Jernej

> ---
> v2:
>  - Drop sun20i-ppu.c which moved
> ---
>  drivers/soc/sunxi/sunxi_sram.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/soc/sunxi/sunxi_sram.c b/drivers/soc/sunxi/sunxi_sram.c
> index 4c4864cd2342..4458b2e0562b 100644
> --- a/drivers/soc/sunxi/sunxi_sram.c
> +++ b/drivers/soc/sunxi/sunxi_sram.c
> @@ -15,7 +15,7 @@
>  #include <linux/module.h>
>  #include <linux/of.h>
>  #include <linux/of_address.h>
> -#include <linux/of_device.h>
> +#include <linux/of_platform.h>
>  #include <linux/platform_device.h>
>  #include <linux/regmap.h>





  parent reply	other threads:[~2023-08-06 11:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 22:42 [PATCH v2 00/23] ARM: DT include cleanups Rob Herring
2023-08-03 22:42 ` [PATCH v2 01/23] ARM: l2x0: Add explicit includes for init and types Rob Herring
2023-08-03 22:42 ` [PATCH v2 02/23] ARM: sti: Drop unused includes Rob Herring
2023-08-04 15:02   ` Patrice CHOTARD
2023-08-03 22:42 ` [PATCH v2 03/23] ARM: alpine: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 04/23] ARM: berlin: " Rob Herring
2023-08-06  9:26   ` Jisheng Zhang
2023-08-03 22:42 ` [PATCH v2 05/23] ARM: dove: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 06/23] ARM: hpe: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 07/23] ARM: mmp: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 08/23] ARM: nomadik: " Rob Herring
2023-08-10  8:18   ` Linus Walleij
2023-08-03 22:42 ` [PATCH v2 09/23] ARM: npcm: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 10/23] ARM: nspire: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 11/23] ARM: pxa: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 12/23] ARM: rockchip: " Rob Herring
2023-08-06 13:41   ` Heiko Stübner
2023-08-03 22:42 ` [PATCH v2 13/23] ARM: versatile: " Rob Herring
2023-08-10  8:19   ` Linus Walleij
2023-08-03 22:42 ` [PATCH v2 14/23] ARM: mvebu: Explicitly include correct DT includes Rob Herring
2023-08-03 22:42 ` [PATCH v2 15/23] ARM: spear: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 16/23] bus: " Rob Herring
2023-08-04 15:11   ` Laurentiu Tudor
2023-08-04 19:08   ` Jernej Škrabec
2023-08-03 22:42 ` [PATCH v2 17/23] firmware: " Rob Herring
2023-08-04  9:51   ` Sudeep Holla
2023-08-03 22:42 ` [PATCH v2 18/23] soc: aspeed: " Rob Herring
2023-08-03 22:42 ` [PATCH v2 19/23] soc: mediatek: " Rob Herring
2023-08-03 22:43 ` [PATCH v2 20/23] soc: rockchip: " Rob Herring
2023-08-03 22:43 ` [PATCH v2 21/23] soc: sunxi: " Rob Herring
2023-08-04 14:38   ` Jernej Škrabec
2023-08-06 11:41   ` Jernej Škrabec [this message]
2023-08-22 22:30     ` Rob Herring
2023-08-22 22:35       ` Rob Herring
2023-08-03 22:43 ` [PATCH v2 22/23] soc: xilinx: " Rob Herring
2023-08-04  6:51   ` Michal Simek
2023-08-03 22:43 ` [PATCH v2 23/23] soc: fsl: " Rob Herring
2023-08-09 13:57 ` (subset) [PATCH v2 00/23] ARM: DT include cleanups Heiko Stuebner

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=5696647.DvuYhMxLoT@jernej-laptop \
    --to=jernej.skrabec@gmail.com \
    --cc=linux-aspeed@lists.ozlabs.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