From: Sasha Levin <sashal@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org
Subject: Re: [PATCH 4.9 00/59] 4.9.226-rc2 review
Date: Tue, 2 Jun 2020 12:33:46 -0400 [thread overview]
Message-ID: <20200602163346.GQ1407771@sasha-vm> (raw)
In-Reply-To: <3c900c0e-b15c-da05-d3d8-e68acf660076@roeck-us.net>
On Tue, Jun 02, 2020 at 08:37:26AM -0700, Guenter Roeck wrote:
>On 6/2/20 3:23 AM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 4.9.226 release.
>> There are 59 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Thu, 04 Jun 2020 10:16:52 +0000.
>> Anything received after that time might be too late.
>>
>
>Many arm builds still fail as attached. Is it really only me seeing this problem ?
>
>FWIW, if we need/want to use unified assembler in v4.9.y, shouldn't all unified
>assembler patches be applied ?
We don't - I took 71f8af111010 as a dependency rather than on its own
merit.
>$ git log --oneline v4.9..c001899a5d6 arch/arm | grep unified
>c001899a5d6c ARM: 8843/1: use unified assembler in headers
>a216376add73 ARM: 8841/1: use unified assembler in macros
>eb7ff9023e4f ARM: 8829/1: spinlock: use unified assembler language syntax
>32fdb046ac43 ARM: 8828/1: uaccess: use unified assembler language syntax
>1293c2b5d790 ARM: dts: berlin2q: add "cache-unified" to l2 node
>75fea300d73a ARM: 8723/2: always assume the "unified" syntax for assembly code
>
>I am quite concerned especially about missing commit 75fea300d73a,
>which removes the ARM_ASM_UNIFIED configuration option. That means it is
>still present in v4.9.y, but the failing builds don't enable it. Given that,
>the build failures don't seem to be surprising.
I'm just going to drop this series from 4.9 for now, until we can figure
out how to do it right.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-06-02 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 10:23 [PATCH 4.9 00/59] 4.9.226-rc2 review Greg Kroah-Hartman
2020-06-02 15:37 ` Guenter Roeck
2020-06-02 16:02 ` Jon Hunter
2020-06-02 16:04 ` Naresh Kamboju
2020-06-02 16:33 ` Sasha Levin [this message]
2020-06-30 21:46 ` Pavel Machek
2020-07-01 6:55 ` Greg Kroah-Hartman
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=20200602163346.GQ1407771@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).