[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdke_HbSrmGO5ThNy4o87G4BhA845QcgZFUTB7m6cBHTDg@mail.gmail.com>
Date: Fri, 15 Feb 2019 11:43:35 -0800
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
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, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
<ard.biesheuvel@...aro.org> wrote:
>
> 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.
If you're referring to
https://www.spinics.net/lists/stable/msg278381.html, that's fair (I
think those were helpful for LLD support on arm64).
Why didn't you speak up then? Why is this coming up now?
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists