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
Date: Tue, 12 Sep 2023 22:20:06 +1000 [thread overview]
Message-ID: <20230912222006.5a7cab3d@canb.auug.org.au> (raw)
In-Reply-To: <20230912112011.GB20408@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi David,
On Tue, 12 Sep 2023 13:20:11 +0200 David Sterba <dsterba@suse.cz> wrote:
>
> 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.
>
> 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.
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-12 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 0:46 linux-next: build warnings after merge of the btrfs tree Stephen Rothwell
2023-09-12 11:20 ` David Sterba
2023-09-12 12:20 ` Stephen Rothwell [this message]
2023-09-20 3:16 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-01-27 1:36 Stephen Rothwell
2020-01-14 22:30 Stephen Rothwell
2020-01-17 16:24 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230912222006.5a7cab3d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox