Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
Date:   Fri, 8 Dec 2023 07:58:47 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Rob Herring <robh@kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the devicetree tree
Message-ID: <20231208075847.6bbd23b8@canb.auug.org.au>
In-Reply-To: <CAL_JsqKXo+Cr=9s=dt1kCQeMadJ_cnuSpm06zmvK8yd-vd2X3g@mail.gmail.com>
References: <20231207125737.5e7553e3@canb.auug.org.au>
        <CAL_JsqKXo+Cr=9s=dt1kCQeMadJ_cnuSpm06zmvK8yd-vd2X3g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/Y5My8QC91/48vQRFjaBW_a+";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/Y5My8QC91/48vQRFjaBW_a+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Rob,

On Thu, 7 Dec 2023 09:11:22 -0600 Rob Herring <robh@kernel.org> wrote:
>
> I'm sending out fixes for all these. I want to get the final patch
> ("of: Stop circularly including of_device.h and of_platform.h") for
> all this in next to get some better build coverage and catch any new
> drivers added. But if it is dropped for every new driver that breaks,
> I'll never get it in. Can you fix these up or just leave them broken?
> I can keep the fixes in my tree until they get applied by the
> corresponding subsystem.

These dependencies between trees are impossible to handle.  Please if
you really need the final patch in, then you must put all the necessary
fixes in the same branch.  There is no telling what order Linus (or I)
will merge the interdependent branches.

The alternative is to spray the needed fixes out to the other
subsystems and then put the final patch in after the merge window
closes or the next release.

I cannot "just leave them broken" because that will interfere with
other's trying to get their work done.  I will try fix up the newly
added drivers if they are obvious, but in the case of these include file
cleanups, that can be quite difficult sometimes.
--=20
Cheers,
Stephen Rothwell

--Sig_/Y5My8QC91/48vQRFjaBW_a+
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmVyMgcACgkQAVBC80lX
0Gyepgf/WasA+iIOtn/ZTy7BHxAZLqhsI7Dhvs+SjIeHrj2cw2iXlXo9cJwAdwAw
h4abJR4iFSOGKmMRz0jwjT99EPZxSu+PNOJzHMH5uPo4+yLrDQ7I8PtH+gzJeaQb
j3RKwRkYQDwPQxvQ2AUHgaOzxyyekthoN7QFz7C0UgX9HUR0oB++OQ5E6foVEUSz
lb2NSZ2OKBmI7h9wYa+S06UnhgNIKv/Uz3nIvrdu6NPSoGsheoHwirP0W/82o4tC
fk3Mn9AKLsJcaohAekMC7dEtDtsAZvov+y6/u9bqY9mtksj3vzoLBL0EesBkH1X1
7UBuhL8gsT/MPOGTpeIDuVLn0EFcUg==
=IU0l
-----END PGP SIGNATURE-----

--Sig_/Y5My8QC91/48vQRFjaBW_a+--