Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Will Deacon <will@kernel.org>
To:     Catalin Marinas <catalin.marinas@arm.com>,
        Rob Herring <robh@kernel.org>
Cc:     kernel-team@android.com, Will Deacon <will@kernel.org>,
        devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Explicitly include correct DT includes
Date:   Mon, 31 Jul 2023 18:44:24 +0100
Message-Id: <169081113966.3427180.6648898239320683110.b4-ty@kernel.org>
In-Reply-To: <20230714174021.4039807-1-robh@kernel.org>
References: <20230714174021.4039807-1-robh@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 14 Jul 2023 11:40:20 -0600, 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.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: Explicitly include correct DT includes
      https://git.kernel.org/arm64/c/b9d601249740

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev