mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	f.fainelli@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH 5.14 000/857] 5.14.19-rc2 review
Date: Tue, 16 Nov 2021 20:40:32 +0000	[thread overview]
Message-ID: <af1e8687-7e6b-1599-a4f0-116d0da616f5@nvidia.com> (raw)
In-Reply-To: <20211116142622.081299270@linuxfoundation.org>


On 16/11/2021 15:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.14.19 release.
> There are 857 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, 18 Nov 2021 14:24:22 +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/v5.x/stable-review/patch-5.14.19-rc2.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.14.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> -------------
> Pseudo-Shortlog of commits:

...

> Mark Brown <broonie@kernel.org>
>      spi: Check we have a spi_device_id for each DT compatible


The above commit generates some new warnings ...

  WARNING KERN SPI driver mtd_dataflash has no spi_device_id for atmel,at45
  WARNING KERN SPI driver mtd_dataflash has no spi_device_id for atmel,dataflash
  WARNING KERN SPI driver mmc_spi has no spi_device_id for mmc-spi-slot

This is causing a boot test to fail on Tegra. I have posted
fixes for these [0][1], but they are yet to be picked up for
mainline.

Jon

Test results for stable-v5.14:
     10 builds:	10 pass, 0 fail
     28 boots:	28 pass, 0 fail
     114 tests:	113 pass, 1 fail

Linux version:	5.14.19-rc2-gc82fd5d7547b
Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
                 tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
                 tegra20-ventana, tegra210-p2371-2180,
                 tegra210-p3450-0000, tegra30-cardhu-a04

Test failures:	tegra194-p2972-0000: boot.py


[0] https://lore.kernel.org/linux-mtd/20211115113655.237785-1-jonathanh@nvidia.com/
[1] https://lore.kernel.org/all/20211115113813.238044-1-jonathanh@nvidia.com/
-- 
nvpublic

  parent reply	other threads:[~2021-11-16 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 15:01 Greg Kroah-Hartman
2021-11-16 18:57 ` Shuah Khan
2021-11-16 20:10 ` Florian Fainelli
2021-11-16 20:40 ` Jon Hunter [this message]
2021-11-17  8:05   ` Greg Kroah-Hartman
2021-11-16 23:22 ` Fox Chen
2021-11-17  4:01 ` Guenter Roeck
2021-11-17  4:16 ` 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=af1e8687-7e6b-1599-a4f0-116d0da616f5@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --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=pavel@denx.de \
    --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

all inboxes | Powered by JetHome®