Date:   Fri, 14 Jan 2022 12:02:40 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Steven Rostedt <rostedt@goodmis.org>
Cc:     Yinan Liu <yinan@linux.alibaba.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 ftrace tree
Message-ID: <20220114120240.4b592480@canb.auug.org.au>
In-Reply-To: <20220112113103.7e03448f@canb.auug.org.au>
References: <20220112113103.7e03448f@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/wnYUD+_he4wYAMN/08IXqt_";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/wnYUD+_he4wYAMN/08IXqt_
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

On Wed, 12 Jan 2022 11:31:03 +1100 Stephen Rothwell <sfr@canb.auug.org.au> =
wrote:
>
> After merging the ftrace tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>=20
> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=3D1 as a workaround
>=20
> I am not sure what caused this - maybe commit
>=20
>   4f1f18311591 ("scripts: ftrace - move the sort-processing in ftrace_ini=
t")
>=20
> I have used the ftrace tree from next-20220111 for today.

I am still getting this.

--=20
Cheers,
Stephen Rothwell

--Sig_/wnYUD+_he4wYAMN/08IXqt_
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmHgy7AACgkQAVBC80lX
0GywVQf+IhUpgidbLaQEOV6MPgWQ8cxv8mMsZ7gaNLc/sYZ1Q7wBv8qA01SxnDCB
xEpML44palAVdC2Vc0hV2NosJjxFPEIM+aCWT1MPPLEp6IYITivuMk8tCZL2ztQ0
l9ityiL4izNpOhi90+7PebKMA1OMHWPgUrPIE8hvwPtSpz1R1ifXbKlvbIXQgYQt
itKdl7/8w0XGR6qPlNystJwzp2K5Sg2M/frxCjvfptCxlXHqALClEibmw1sYdGiR
wmfog3D8SrRV34cLemugYx/xuy1CYlY7ytjWSHfye7PVit1OwlVQlOuIEBfEY2cv
26hvv6DGrm/8psO20RYr9XoXeApGaA==
=9VNf
-----END PGP SIGNATURE-----

--Sig_/wnYUD+_he4wYAMN/08IXqt_--