mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
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@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	Vegard Nossum <vegard.nossum@oracle.com>,
	Darren Kenny <darren.kenny@oracle.com>
Subject: Re: [PATCH 6.12 000/172] 6.12.6-rc1 review
Date: Thu, 19 Dec 2024 12:05:55 +0530	[thread overview]
Message-ID: <f8083d59-7f38-4f12-9b53-1ad0d2826a4a@oracle.com> (raw)
In-Reply-To: <20241217170546.209657098@linuxfoundation.org>

Hi Greg,

On 17/12/24 22:35, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.12.6 release.
> There are 172 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, 19 Dec 2024 17:05:03 +0000.
> Anything received after that time might be too late.

We now made tests for 6.12.y stable rc testing ready.

No problems seen on x86_64 and aarch64 with our testing.
(Boot/ Install/ LTP so far)

We do see some problems with failing kselftests, will investigate them 
and report them here. They are not specific to 6.12.6, most of them were 
reproducible on 6.12.5, but we will have to look at all of the failing 
kselftests before reporting.

Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>

Thanks,
Harshit

  parent reply	other threads:[~2024-12-19  6:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 17:05 Greg Kroah-Hartman
2024-12-17 20:21 ` Florian Fainelli
2024-12-17 22:58 ` Shuah Khan
2024-12-17 23:43 ` Christian Heusel
2024-12-18  0:58   ` Guenter Roeck
2024-12-18  6:42 ` Ron Economos
2024-12-18 12:16 ` Takeshi Ogasawara
2024-12-18 12:32 ` Mark Brown
2024-12-18 13:03 ` Peter Schneider
2024-12-18 13:19 ` Naresh Kamboju
2024-12-18 14:56   ` Jiri Slaby
2024-12-18 16:53     ` Guenter Roeck
2024-12-18 16:54       ` Peter Zijlstra
2024-12-18 17:48         ` Jiri Slaby
2024-12-19  5:56           ` Guenter Roeck
2025-01-13 11:00         ` Pavel Machek
2024-12-18 17:21 ` Jon Hunter
2024-12-18 17:57 ` Justin Forbes
2024-12-19  6:35 ` Harshit Mogalapalli [this message]
2024-12-19 18:29 ` Miguel Ojeda
2024-12-17 18:09 Ronald Warsow

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=f8083d59-7f38-4f12-9b53-1ad0d2826a4a@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=darren.kenny@oracle.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@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 \
    --cc=vegard.nossum@oracle.com \
    /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®