Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34;
Date:   Fri, 8 Dec 2023 14:11:56 +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: <20231208141156.20341c10@canb.auug.org.au>
In-Reply-To: <CAL_JsqKyqe827YRyqZnqcVghhuAuvWoiS4U7uR8wwYoGj3=9KA@mail.gmail.com>
References: <20231207125737.5e7553e3@canb.auug.org.au>
        <CAL_JsqKXo+Cr=9s=dt1kCQeMadJ_cnuSpm06zmvK8yd-vd2X3g@mail.gmail.com>
        <20231208075847.6bbd23b8@canb.auug.org.au>
        <CAL_JsqKyqe827YRyqZnqcVghhuAuvWoiS4U7uR8wwYoGj3=9KA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/1u9Ex+aSgYAkr2kJerTwxtH";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/1u9Ex+aSgYAkr2kJerTwxtH
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Rob,

On Thu, 7 Dec 2023 16:05:27 -0600 Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Dec 7, 2023 at 2:58=E2=80=AFPM Stephen Rothwell <sfr@canb.auug.or=
g.au> wrote:
> >
> > On Thu, 7 Dec 2023 09:11:22 -0600 Rob Herring <robh@kernel.org> wrote: =
=20
> > >
> > > 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. =20
> >
> > 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. =20
>=20
> Yes, that's what I've been doing since July and plan to do for the
> final patch. The final patch can't wait a cycle because then we'll
> just have more moles to wack. There's a couple of dependencies that
> still haven't been picked up (seems Sparc is unmaintained), so I'm
> going to send those along. I'll carry any further fixes until they I
> see they are applied.

OK, so I have moved your tree to be merged last and I fixed up the new
driver, so hopefully we are good, now.
--=20
Cheers,
Stephen Rothwell

--Sig_/1u9Ex+aSgYAkr2kJerTwxtH
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmVyiXwACgkQAVBC80lX
0GxmdAf7BqaIpe3WGH5SKEELLOV19V03pACUoh5AkIb2ZbKHd0e2JIhwMx35pibl
DfcWXgRRCAQqDt0HfWTI0jUBpzzp1eMRW/O3t0A29obWDM+JRG5JZWiyJOo6Zelq
ElhogKs/w9Y9rU3ojIoPlTMOLxggBCnR1M+B7n5WkXGIJYBezJYNYVL0BhMO9loG
sr0DeiCQioayE8ibr+ov19c6ejjTBTslcdiE2w505fEei3LGpTz8Hc6KeXhz0bKH
ck1sU10lV8H0mTEC2a+5OHadAvou9ITYPT5QdnHlWSXna4mx6I5qru1u0lLYi4KE
DD1oESM4ptz1wOX7nR7fGb/So5kCcA==
=9eEw
-----END PGP SIGNATURE-----

--Sig_/1u9Ex+aSgYAkr2kJerTwxtH--