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:   Fri, 13 Jan 2023 10:36:54 +1100
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: linux-next: build failure after merge of the btrfs tree
Message-ID: <20230113103654.5cbc1d54@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/WgQeCgdymxyNKSpH4wF288s";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

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

Hi all,

After merging the btrfs tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

fs/btrfs/disk-io.c: In function 'btrfs_init_fs_root':
fs/btrfs/disk-io.c:1531:22: warning: unused variable 'nofs_flag' [-Wunused-=
variable]
 1531 |         unsigned int nofs_flag;
      |                      ^~~~~~~~~

Caused by commit

  1556cd3d099a ("btrfs: locking: use atomic for DREW lock writers")

I have used the btrfs tree from next-20230112 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/WgQeCgdymxyNKSpH4wF288s
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmPAmZcACgkQAVBC80lX
0Gw+Bgf/f31vqhlOCL84m71We2covOd4wR0wZ8etWd9YZvsYOTLu3A0vEHJH7bbE
1eH6o8FPyEYjBmLiQl8Lq++BWZTaZLc9MyM88QkGQ4xbyewtsjhx7C3V5xsoumi0
cKc4JBtfR6fx9vMrkF0NzLfO3/UNsgyAOJ1huj9QTpOsTMRihcq12ad8VdIvlTjS
dyy3KaoIExfzx5eWS0F2rLt+OxwBmtvxSkyxaHq/yBnYF+//THuStBiYlMft9Ksz
+fMRK3pHVQ2ukovAfkQuE7FRr/YFVtivrIRBe4Y7/yuX6sSux2WOJlbQLzxuajH3
DWTTqzbpG1qS7B5tHGCGiSVtppx+cg==
=C5Bn
-----END PGP SIGNATURE-----

--Sig_/WgQeCgdymxyNKSpH4wF288s--