Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Date:   Wed, 20 Sep 2023 13:16:42 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     David Sterba <dsterba@suse.cz>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the btrfs tree
Message-ID: <20230920131642.62803bd8@canb.auug.org.au>
In-Reply-To: <20230912222006.5a7cab3d@canb.auug.org.au>
References: <20230912104646.3a9140f7@canb.auug.org.au>
        <20230912112011.GB20408@suse.cz>
        <20230912222006.5a7cab3d@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/FAG_enEudv=Du=Dqq6jepBd";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/FAG_enEudv=Du=Dqq6jepBd
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Stephen,

On Tue, 12 Sep 2023 22:20:06 +1000 Stephen Rothwell <sfr@canb.auug.org.au> =
wrote:
>
> Hi David,
>=20
> On Tue, 12 Sep 2023 13:20:11 +0200 David Sterba <dsterba@suse.cz> wrote:
> >=20
> > I tried 12 and 13, no warnings on x86_64, however the report is on
> > powerpc. If this is on a big endian host it could be a valid warning, we
> > have an optmization where the on-disk format endianity matches CPU
> > (little endian) then the structures btrfs_disk_key and btrfs_key are
> > equivalent and no coversion is needed.
> >=20
> > There were some changes that might be related and newly added to
> > for-next so we don't have any other reference point, I'll take a look. =
=20
>=20
> This is indeed a big endian build (big endian cross build on a little
> endian host).  I also did *not* get these warnings on my x86_64 build.

But I do get them from my s390 defconfig build.  Any progress?

--=20
Cheers,
Stephen Rothwell

--Sig_/FAG_enEudv=Du=Dqq6jepBd
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmUKZBoACgkQAVBC80lX
0Gy70gf/YmluHlhMP7eWESvTvE/NAroQsV7JJwxxnANNjjFzVbgss+VXC73QpW4e
ZdxoxMPNvpb+I6dejb7+rmpjYYaW7VLgH2oT+Zqdq8GM6wRP3ULiBMQVoKK85DPC
mzh9eb0mrbvdCr125ix4ShAdofmIdQMTIALnfASi4ffCxq/lStlBZGEXeasbUdcS
pzQxGGWjDtmgvVkGlee8h6hI4LZw9M8ebiiW9mFlc1+efNHDODSU8V6IP441dQs2
mNNr+JsXiYO8i2AmSKOZ0BVSmPUVS7mwYe0dvYQJDLsJdQ0wZtgE9wpJYvjsr/n5
Xf9Ua6vidk8lxb0X1x9NpWKxisxMag==
=lDmk
-----END PGP SIGNATURE-----

--Sig_/FAG_enEudv=Du=Dqq6jepBd--