From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 4.19 000/321] 4.19.88-stable review
Date: Wed, 4 Dec 2019 14:53:24 +0000 [thread overview]
Message-ID: <4f1552b1-ff6b-7342-b66e-04685aacf6ea@nvidia.com> (raw)
In-Reply-To: <20191204112936.GA3565947@kroah.com>
On 04/12/2019 11:29, Greg Kroah-Hartman wrote:
> On Wed, Dec 04, 2019 at 09:45:31AM +0000, Jon Hunter wrote:
>>
>> On 03/12/2019 22:31, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 4.19.88 release.
>>> There are 321 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, 05 Dec 2019 22:30:32 +0000.
>>> Anything received after that time might be too late.
>>>
>>> The whole patch series can be found in one patch at:
>>> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.88-rc1.gz
>>> or in the git tree and branch at:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>> -------------
>>> Pseudo-Shortlog of commits:
>>
>> ...
>>
>>> Ding Tao <miyatsu@qq.com>
>>> arm64: dts: marvell: armada-37xx: Enable emmc on espressobin
>>
>> The above commit is causing the following build failure for ARM64 ...
>>
>> DTC arch/arm64/boot/dts/marvell/armada-3720-espressobin.dtb
>> arch/arm64/boot/dts/marvell/armada-3720-espressobin.dtb: ERROR
>> (phandle_references): /soc/internal-regs@d0000000/sdhci@d0000: Reference
>> to non-existent node or label "sdio_pins"
>>
>> arch/arm64/boot/dts/marvell/armada-3720-espressobin.dtb: ERROR
>> (phandle_references): /soc/internal-regs@d0000000/sdhci@d8000: Reference
>> to non-existent node or label "mmc_pins"
>
> Thanks for letting me know, I'll go drop this one and push out a -rc2
> with that removed.
Great! All tests now passing for Tegra ...
Test results for stable-v4.19:
13 builds: 13 pass, 0 fail
22 boots: 22 pass, 0 fail
32 tests: 32 pass, 0 fail
Linux version: 4.19.88-rc2-gba731ec12c66
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2019-12-04 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191203223427.103571230@linuxfoundation.org>
2019-12-04 9:45 ` [PATCH 4.19 000/321] 4.19.88-stable review Jon Hunter
2019-12-04 11:29 ` Greg Kroah-Hartman
2019-12-04 14:53 ` Jon Hunter [this message]
2019-12-04 17:18 ` Greg Kroah-Hartman
2019-12-04 19:11 ` Naresh Kamboju
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=4f1552b1-ff6b-7342-b66e-04685aacf6ea@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-tegra@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