From: Jisheng Zhang <jszhang@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 04/23] ARM: berlin: Drop unused includes
Date: Sun, 6 Aug 2023 17:26:09 +0800 [thread overview]
Message-ID: <ZM9nMTHTFEY8JcC/@xhacker> (raw)
In-Reply-To: <20230803-dt-header-cleanups-for-soc-v2-4-d8de2cc88bff@kernel.org>
On Thu, Aug 03, 2023 at 04:42:44PM -0600, Rob Herring wrote:
> Several includes are not needed, so drop them.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
Reviewed-by: Jisheng Zhang <jszhang@kernel.org>
Thanks!
PS: what would be the better merge path? Arnd take it directly with each
sub-maintainers' ack or something else?
> ---
> arch/arm/mach-berlin/berlin.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/arm/mach-berlin/berlin.c b/arch/arm/mach-berlin/berlin.c
> index 2424ad40190c..13d5c899f09e 100644
> --- a/arch/arm/mach-berlin/berlin.c
> +++ b/arch/arm/mach-berlin/berlin.c
> @@ -8,11 +8,6 @@
> * (c) Marvell International Ltd.
> */
>
> -#include <linux/init.h>
> -#include <linux/io.h>
> -#include <linux/kernel.h>
> -#include <linux/of_platform.h>
> -#include <asm/hardware/cache-l2x0.h>
> #include <asm/mach/arch.h>
>
> static const char * const berlin_dt_compat[] = {
>
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-08-06 9:26 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 [this message]
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
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=ZM9nMTHTFEY8JcC/@xhacker \
--to=jszhang@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).