Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 12 Feb 2019 07:18:58 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        Jaegeuk Kim <jaegeuk@kernel.org>,
        Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 4.20 081/352] f2fs: avoid build warn of fall_through
Message-ID: <20190212071858.1a6a43c4@canb.auug.org.au>
In-Reply-To: <20190211141851.175526205@linuxfoundation.org>
References: <20190211141846.543045703@linuxfoundation.org>
        <20190211141851.175526205@linuxfoundation.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/UO4lzIyFLO0fEJ_yV8qfr1="; protocol="application/pgp-signature"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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

Hi Greg,

On Mon, 11 Feb 2019 15:15:08 +0100 Greg Kroah-Hartman <gregkh@linuxfoundati=
on.org> wrote:
>
> 4.20-stable review patch.  If anyone has any objections, please let me kn=
ow.
>=20
> ------------------
>=20
> [ Upstream commit f5d5510e7389fa264337fb524346bac9eb93adc8 ]
>=20
> After merging the f2fs tree, today's linux-next build
>  (x86_64_allmodconfig) produced this warning:
>=20
>  In file included from fs/f2fs/dir.c:11:
>  fs/f2fs/f2fs.h: In function '__mark_inode_dirty_flag':
>  fs/f2fs/f2fs.h:2388:6: warning: this statement may fall through [-Wimpli=
cit-fallthrough=3D]
>     if (set)
>        ^
>  fs/f2fs/f2fs.h:2390:2: note: here
>    case FI_DATA_EXIST:
>    ^~~~
>=20
>  Exposed by my use of -Wimplicit-fallthrough

Does the 4.20 stable tree use -Wimplicit-fallthrough?  I assume not
(since v4.20 doesn't), so this warning does not happen in that tree.
--=20
Cheers,
Stephen Rothwell

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

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlxh2LIACgkQAVBC80lX
0Gwjlgf/ZkViUA6N9NOj11cEp/+ji/zMBm7WXvhpntX8fYgWO1AO3AZAO1AVgizB
pqsHqD69UdCFjPhr4rhnZrUY1GjoCvgrx9lFPtcSyfUwuoFI0O6QrM/VGJXXZEN6
IeiGVFkuHxZxDRSIHoYgRVZgA651tj3Z2F2xNoDKZNgrbZxBBTutMg2jD+Kjqs9S
XN5rGJYIHV9l1D4ULZlZvS5si8SiURbF1g25MTiKoBH0ghtdOs4fqAAJ7/CFrRqo
pfbFCfFy4hUxITM5E92zYfQtqJB+gVf/DqJbsd3+sTv++C0uttYgdxIDMlqqKEgt
Asgj6b4mkFoap06BTzQ4VwvLOz5FPQ==
=FK7G
-----END PGP SIGNATURE-----

--Sig_/UO4lzIyFLO0fEJ_yV8qfr1=--