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:   Tue, 23 Aug 2022 17:03:58 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Nathan Chancellor <nathan@kernel.org>
Cc:     Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
        Liam Girdwood <lgirdwood@gmail.com>,
        Claudiu Beznea <claudiu.beznea@microchip.com>,
        alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org,
        Nicolas Ferre <nicolas.ferre@microchip.com>,
        llvm@lists.linux.dev,
        Alexandre Belloni <alexandre.belloni@bootlin.com>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Tom Rix <trix@redhat.com>
Subject: Re: [PATCH] ASoC: mchp-spdiftx: Fix clang
 -Wbitfield-constant-conversion
Message-ID: <YwT6bmqeBeoYcRi7@sirena.org.uk>
References: <20220810010809.2024482-1-nathan@kernel.org>
 <166058059542.769843.4941839393289864947.b4-ty@kernel.org>
 <YwT0oUjo/lzBDRdH@dev-arch.thelio-3990X>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="bRD/piUAUlQcMCKB"
Content-Disposition: inline
In-Reply-To: <YwT0oUjo/lzBDRdH@dev-arch.thelio-3990X>
Precedence: bulk


--bRD/piUAUlQcMCKB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Aug 23, 2022 at 08:39:13AM -0700, Nathan Chancellor wrote:

> I noticed that this was applied to for-6.1. I know you do not rebase or
> change your trees so this request might be rejected based on that alone
> but would it be possible to cherry-pick this to for-6.0 so that it can
> be applied to Linus's tree quicker? We have had to apply this change to
> our CI to keep our builds green in mainline, -tip, and 5.19/5.15 stable
> with clang-16 due to -Werror. If not, no worries, I should have made it
> clearer that is what I was looking for with the subject prefix.

Hrm, OK - it's a bit surprising that this didn't get fixed in -next
before the clang change made it to mainline TBH, it looked like
something that had just hit -next.

--bRD/piUAUlQcMCKB
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmME+m4ACgkQJNaLcl1U
h9DGGAf9FQ1B6+3Dfsp8LkqcAvNpYaPcgLbadzxOSiNhCz3nKbqjHeLn7qgXzCSi
ZsLpU8FfqcWvIzvDuDUt/lAFh2GEDS04od0HLNJ81imVRVaywR9qlc96Mpm+Ist2
Cz4yEkb9Ydw0kZCXXehsIPlCFtNVu5AKKHJJpgn6YFFjem/IMkeKrftmsIsMoQ6F
bfS+p2h7dJVYPOpEWSm3wAr2zrknfATV9SlDJcHqGd1E5GiKi3s3flgUpip2qHaX
g62kCwtHXs14FD+lbhUmIw3YxQyRrfQYXMosmDoNlvl7SahsauyoeRxgh3bCR0vk
GGUbcahF77/1Pzn+McWxNTRucJ2ueg==
=Xfht
-----END PGP SIGNATURE-----

--bRD/piUAUlQcMCKB--