From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Will Deacon <will.deacon@arm.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Sandeep Patil <sspatil@google.com>
Subject: Re: [PATCH] arm64/neon: Disable -Wincompatible-pointer-types when building with Clang
Date: Tue, 19 Feb 2019 12:35:16 +0100 [thread overview]
Message-ID: <CAKv+Gu9v3htHyfCZvDU2Qd8vQozbBQVeHyyNsrdrwO2r7ReBwA@mail.gmail.com> (raw)
In-Reply-To: <20190219111927.GA17012@kroah.com>
On Tue, 19 Feb 2019 at 12:19, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Feb 19, 2019 at 11:35:12AM +0100, Ard Biesheuvel wrote:
> > On Fri, 15 Feb 2019 at 20:45, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > >
> > > On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers <ndesaulniers@google.com> wrote:
> > > >
> > > > On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
> > > > <ard.biesheuvel@linaro.org> wrote:
> > > > >
> > > > > On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers <ndesaulniers@google.com> wrote:
> > > > > >
> > > > > > On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> > > > > > <ard.biesheuvel@linaro.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?
> > >
> > > That is just one example, and I failed to realise it at the time.
> > >
> > > I think the Clang/LLVM work you are doing is very important, but I
> > > simply don't think any of it belongs in -stable kernels.
> >
> > OK, to clarify my position:
> >
> > I have no problem whatsoever with taking this patch into v5.x, so
> >
> > Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > but going forward, I will push back on -stable backports for
> > Clang/LLVM specific changes, since they are obviously in violation of
> > the stable kernel rules.
>
> Getting older kernels to build/run properly on newer compilers is just a
> part of life for the stable trees. If you note, we have done a lot of
> gcc7, then gcc8, and clang patches backported over the years in order to
> make it possible for people (like me and my testing infrastructure at
> the least) to keep building these old kernels on newer systems.
>
> So while it's not part of the "documented" rules, I do take this type of
> change, as it does help out a huge population of users and testers.
>
That doesn't make a lot of sense to me, but that is the common
practice, then I won't object any longer.
prev parent reply other threads:[~2019-02-19 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 1:39 Nathan Chancellor
2019-02-15 11:50 ` Mark Brown
2019-02-15 18:50 ` Will Deacon
2019-02-15 19:20 ` Ard Biesheuvel
2019-02-15 19:25 ` Nick Desaulniers
2019-02-15 19:28 ` Ard Biesheuvel
2019-02-15 19:43 ` Nick Desaulniers
2019-02-15 19:45 ` Ard Biesheuvel
2019-02-19 10:35 ` Ard Biesheuvel
2019-02-19 11:19 ` Greg KH
2019-02-19 11:35 ` Ard Biesheuvel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKv+Gu9v3htHyfCZvDU2Qd8vQozbBQVeHyyNsrdrwO2r7ReBwA@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sspatil@google.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®