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;
Date:   Tue, 13 Dec 2022 13:45:29 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Kefeng Wang <wangkefeng.wang@huawei.com>,
        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 mm-hotfixes tree
Message-ID: <20221213134529.451b45a3@canb.auug.org.au>
In-Reply-To: <20221212182304.fc148bf08bc17e58ec4b6674@linux-foundation.org>
References: <20221213093054.5211da74@canb.auug.org.au>
        <e8dfaf60-ff35-66d3-7bc1-f11eaaef642a@huawei.com>
        <20221212182304.fc148bf08bc17e58ec4b6674@linux-foundation.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/1823e1rK=+hVA3PrWAmmOVb";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/1823e1rK=+hVA3PrWAmmOVb
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Andrew,

On Mon, 12 Dec 2022 18:23:04 -0800 Andrew Morton <akpm@linux-foundation.org=
> wrote:
>
> On Tue, 13 Dec 2022 09:34:24 +0800 Kefeng Wang <wangkefeng.wang@huawei.co=
m> wrote:
>=20
> > Hi, this patch relays on Tony Luck's Patch series "Copy-on-write poison=
=20
> > recovery".[1]
> > and tested ppc64_defconfig based on next-20221208, it's no build failur=
e =20
>=20
> I reordered these a couple of days ago, not sure how Stephen got a hold
> of this tree - perhaps I wasn't pushy enough.

Probably, its just what I got when I fetched your branches this morning
(my time).

> Stephen, quoting the mm-everything tag would be helpful, but rarely
> useful so only if you're feeling bored ;)

OK, I will try to remember.

Part of the problem (for me) is that you sometimes update all your
branches in the middle of my day (I am not asking you to stop doing
that - I can cope), so the mm-hotifxes that I have merged early on does
not match the new mm-hotfixes-* branches that get merged as part of mm
(mm-everything) later in the day.  This occasionally causes conflicts,
but they are invariably trivial and fixed by using the versions of
files from the new branches.  I am wondering if maybe I should merge
mm-everything early (but after I have merged and tested all the -fixes
branches) to narrow the race condition :-)

--=20
Cheers,
Stephen Rothwell

--Sig_/1823e1rK=+hVA3PrWAmmOVb
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmOX50kACgkQAVBC80lX
0GzjpQgAkz0xN/fD+oIjtUhSCZWTiw5/qZIZetObd5VuP4yyziYOXtk/IMCYBdOC
klggtrkTkPoo0RLYd6Mqk0uxoh65KMQoQkiBqiRfZNoL/PuSPe5HLl0y8Jiv/1v9
phv2DbhT4Wfuru6uIBc984B4LUWJ9+rA7QVbHQazxO9RtVtstsvN/txO5TW/S05E
K5LuEyvYR7/Wv59ZaVFQBQdxXfGhw7sgjKd3KHmNTjpirty5/yksmdFfa7/9oot4
VPWBnbFpgSm5roDqZfmnbNDtg+F8fsj7CMF7k4Dj3NzXvIMjeOIj0UWrGyLrD5Zl
tHPbZEBEoK0nDVMoV4fmq71QUEvEEw==
=zjVK
-----END PGP SIGNATURE-----

--Sig_/1823e1rK=+hVA3PrWAmmOVb--