From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: Clang patches for 4.9
Date: Mon, 25 Feb 2019 15:55:02 +0100 [thread overview]
Message-ID: <20190225145502.GA16015@kroah.com> (raw)
In-Reply-To: <20190225061301.GA23411@archlinux-ryzen>
On Sun, Feb 24, 2019 at 11:13:01PM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
>
> Attached are three mbox files containing patches that bring the Clang
> backports that Nick did in 4.9.139 up to date with what is currently in
> 4.14 and mainline, as well as fix warnings that are present in the arm64
> and x86_64 defconfigs here and in AOSP (cuttlefish_defconfig). All of
> these warnings are fixed in 4.14 so there will be no regressions from
> upgrading.
>
> They were tested with Arch Linux's GCC 8.2.1 and AOSP's clang-r349610 [1]
> and boot tested in QEMU 3.1.0 with our rootfs files [2].
I've included most of these now, except for the ones already pointed
out.
> Additionally, for Greg, I have provided a merge resolution for
> the Makefile conflict you will get when doing the android-4.9 merge.
> You will also get a conflict in arch/arm64/include/asm/arch_gicv3.h,
> just check out to MERGE_HEAD as the {read,write}_sysreg_s macros have
> the LTO workaround that causes the conflict in the first place. I
> tested this resolution by building and booting cuttlefish_defconfig
> for arm64 with CONFIG_LTO_CLANG and CONFIG_CFI_CLANG enabled.
Thanks for the merge resolution, I am guessing it is not going to be the
same now that I did not take all of your Makefile patches :)
greg k-h
prev parent reply other threads:[~2019-02-25 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 6:13 Clang patches for 4.9 Nathan Chancellor
2019-02-25 14:45 ` Greg Kroah-Hartman
2019-02-25 14:47 ` Greg Kroah-Hartman
2019-02-25 17:35 ` Nathan Chancellor
2019-02-25 17:46 ` Nick Desaulniers
2019-02-25 17:55 ` Nathan Chancellor
2019-02-25 17:56 ` Greg Kroah-Hartman
2019-02-25 14:55 ` Greg Kroah-Hartman [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=20190225145502.GA16015@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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