From: Jon Hunter <jonathanh@nvidia.com>
To: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Cc: <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 17:02:00 +0100 [thread overview]
Message-ID: <ecef7839-1e7e-21aa-66f3-920ad2aa190f@nvidia.com> (raw)
In-Reply-To: <3c900c0e-b15c-da05-d3d8-e68acf660076@roeck-us.net>
On 02/06/2020 16:37, 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 ?
No I am seeing this as well. Been having some email problems today ...
> FWIW, if we need/want to use unified assembler in v4.9.y, shouldn't all unified
> assembler patches be applied ?
>
> $ git log --oneline v4.9..c001899a5d6 arch/arm | grep unified
> c001899a5d6c ARM: 8843/1: use unified assembler in headers
Bisect points to this one for me.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2020-06-02 16:02 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 [this message]
2020-06-02 16:04 ` Naresh Kamboju
2020-06-02 16:33 ` Sasha Levin
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=ecef7839-1e7e-21aa-66f3-920ad2aa190f@nvidia.com \
--to=jonathanh@nvidia.com \
--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).