patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, 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, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.7 000/127] 6.7.5-rc2 review
Date: Thu, 15 Feb 2024 12:27:14 +0100	[thread overview]
Message-ID: <2024021556-pungent-huddle-8204@gregkh> (raw)
In-Reply-To: <4cc8718f-6035-49f7-bd50-39564ac4fba4@nvidia.com>

On Thu, Feb 15, 2024 at 11:14:22AM +0000, Jon Hunter wrote:
> 
> On 14/02/2024 14:29, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.7.5 release.
> > There are 127 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 Fri, 16 Feb 2024 14:22:16 +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/v6.x/stable-review/patch-6.7.5-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-6.7.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> 
> No new regressions for Tegra ...
> 
> Test results for stable-v6.7:
>     10 builds:    10 pass, 0 fail
>     26 boots:     26 pass, 0 fail
>     116 tests:    115 pass, 1 fail
> 
> Linux version:    6.7.5-rc2-gc94a8b48bd4b
> 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:    tegra186-p2771-0000: pm-system-suspend.sh

Is this on track to be fixed anywhere in Linus's tree yet?

thanks for testing,

greg k-h

  reply	other threads:[~2024-02-15 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 14:29 [PATCH 6.7 000/127] 6.7.5-rc2 review Greg Kroah-Hartman
2024-02-14 16:07 ` Luna Jernberg
2024-02-14 23:28 ` Allen
2024-02-15  0:22 ` Florian Fainelli
2024-02-15  8:08 ` Naresh Kamboju
2024-02-15 11:14 ` Jon Hunter
2024-02-15 11:27   ` Greg Kroah-Hartman [this message]
2024-02-15 11:44     ` Jon Hunter
2024-02-15 15:45 ` Justin Forbes

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=2024021556-pungent-huddle-8204@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --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=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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).