From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Nick Desaulniers" <ndesaulniers@google.com>,
"# 3.4.x" <stable@vger.kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
nico@linaro.org, "Russell King" <rmk+kernel@armlinux.org.uk>,
"Miles Chen (陳民樺)" <Miles.Chen@mediatek.com>
Subject: Re: please cherry pick 75fea300d73a to 4.14.y
Date: Sat, 15 Feb 2020 15:23:58 -0500 [thread overview]
Message-ID: <20200215202358.GJ1734@sasha-vm> (raw)
In-Reply-To: <20200213192322.GA3778561@kroah.com>
On Thu, Feb 13, 2020 at 11:23:22AM -0800, Greg KH wrote:
>On Thu, Feb 13, 2020 at 11:19:16AM -0800, Nick Desaulniers wrote:
>> Hi Greg, Sasha,
>> Would you please cherry pick
>> commit 75fea300d73a ("ARM: 8723/2: always assume the "unified" syntax
>> for assembly code")
>> which first landed in v4.16-rc1 into 4.14.y?
>>
>> In my experience, it cherry-picks cleanly. It fixes a stream of
>> warnings we see when building 32b ARM kernels with Clang, like:
>>
>> /tmp/signal-1ac549.s: Assembler messages:
>> /tmp/signal-1ac549.s:76: conditional infixes are deprecated in unified syntax
>>
>> We'll make immediate use of it in Android; if anyone objects to
>> landing in stable let us know and we can carry it out of tree.
>
>Seems sane, I'll queue it up after this latest round of stable kernels
>are released in a few days.
I've queued this one on 4.14.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-15 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 19:19 please cherry pick 75fea300d73a to 4.14.y Nick Desaulniers
2020-02-13 19:23 ` Greg KH
2020-02-15 20:23 ` Sasha Levin [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=20200215202358.GJ1734@sasha-vm \
--to=sashal@kernel.org \
--cc=Miles.Chen@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=ndesaulniers@google.com \
--cc=nico@linaro.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robin.murphy@arm.com \
--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