[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKv+Gu-41fhEfJF+pvfCQRqXs4vYPHs77rkJo9=X8Y23QVd6Tw@mail.gmail.com>
Date: Fri, 15 Feb 2019 20:28:23 +0100
From: Ard Biesheuvel <ard.biesheuvel@...aro.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Will Deacon <will.deacon@....com>,
Nathan Chancellor <natechancellor@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Mark Brown <broonie@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kevin Hilman <khilman@...libre.com>,
Sandeep Patil <sspatil@...gle.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] arm64/neon: Disable -Wincompatible-pointer-types when
building with Clang
On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers <ndesaulniers@...gle.com> wrote:
>
> On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> <ard.biesheuvel@...aro.org> wrote:
> > Provided that we stop sending Clang enablement patches to -stable:
>
> What does that mean? We're trying to provide clang support back to
> 4.4 LTS branches. (so 4.4, 4.9, 4.14, 4.19).
I understand that is what you are attempting, but that does not mean
it /belongs/ in -stable.
There are rules for stable, and people that track stable kernels (such
as the distros) should be able to rely on us to only backport bug
fixes, not linker script changes and other updates that fix issues
that did not exist when those kernels were released.
It is unclear to me how these clang changes benefit those users.
Powered by blists - more mailing lists