All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: 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@nabladev.com,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	achill@achill.org, sr@sladewatkins.com,
	linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.1 0000/1879] 6.1.191-rc2 review
Date: Sun, 1 Nov 2026 14:22:10 +0100	[thread overview]
Message-ID: <2026110101-carnivore-harsh-fe38@gregkh> (raw)
In-Reply-To: <7e927599-10b7-44f4-828f-e50c0caf5f27@nvidia.com>

On Sat, Oct 31, 2026 at 02:41:43PM +0000, Jon Hunter wrote:
> Hi Greg,
> 
> On 31/10/2026 09:26, Jon Hunter wrote:
> 
> ...
> 
> > On 31/10/2026 09:24, Jon Hunter wrote:
> >> On Thu, 29 Oct 2026 08:33:04 +0100, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 6.1.191 release.
> >>> There are 1879 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 Sat, 31 Oct 2026 07:28:30 +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.1.191-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.1.y
> >>> and the diffstat can be found below.
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>
> >> Failures detected for Tegra ...
> >>
> >> Test results for stable-v6.1:
> >>     builds:	9 pass, 0 fail
> >>     boots:	28 pass, 4 fail
> >>     tests:	83 pass, 7 fail
> >>
> >> Linux version:	6.1.191-rc2-g3b00df762ebc
> >> Boards tested:	tegra20-ventana
> >>                 tegra30-cardhu-a04
> >>                 tegra124-jetson-tk1
> >>                 tegra210-p2371-2180
> >>                 tegra210-p3450-0000
> >>                 tegra186-p2771-0000
> >>                 tegra186-p3509-0000+p3636-0001
> >>                 tegra194-p2972-0000
> >>                 tegra194-p3509-0000+p3668-0000
> >>
> >> Boot failures:	tegra186-p2771-0000, tegra186-p3509-0000+p3636-0001,
> >>                 tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000
> >>
> >> Test failures:	tegra124-jetson-tk1: pm-system-suspend.sh
> >>                 tegra20-ventana: pm-system-suspend.sh
> >>                 tegra30-cardhu-a04: pm-system-suspend.sh
> > I am looking into the above boot and suspend issues and will let you
> > know what I find.
> 
> Bisecting is pointing to the below commit and reverting it fixes
> the above issues ...
> 
> # first bad commit: [26c5e136ba4e94ad708333c9bd34039a1de397b0] net: stmmac: protect updates of 64-bit statistics counters

Thanks, I've reverted that one now.

greg k-h

  reply	other threads:[~2026-11-01 13:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  7:33 [PATCH 6.1 0000/1879] 6.1.191-rc2 review Greg Kroah-Hartman
2026-10-29  8:29 ` Brett A C Sheffield
2026-10-29 10:10 ` Pavel Machek
2026-10-29 13:09 ` Miguel Ojeda
2026-10-29 14:42 ` Ron Economos
2026-10-29 14:47 ` SJ Park
2026-10-29 15:47 ` Peter Schneider
2026-10-29 18:16 ` Florian Fainelli
2026-10-30  8:47   ` Greg Kroah-Hartman
2026-10-30  8:01 ` Barry K. Nathan
     [not found] ` <b85e0697-d669-4b14-859f-52ee295264e4@rnnvmail201.nvidia.com>
2026-10-31  9:26   ` Jon Hunter
2026-10-31 14:41     ` Jon Hunter
2026-11-01 13:22       ` Greg Kroah-Hartman [this message]
2026-11-02 14:34         ` Jon Hunter
2026-11-03 14:51           ` Sasha Levin
2026-11-01 14:43       ` Sasha Levin
2026-11-02 14:34         ` Jon Hunter
2026-11-03 14:51           ` Sasha Levin

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=2026110101-carnivore-harsh-fe38@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.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@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.