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.6 000/356] 6.6.66-rc1 review
Date: Sat, 14 Dec 2024 18:15:47 +0530 [thread overview]
Message-ID: <30e84dd5-bda1-461e-8401-c0c2177d6c57@oracle.com> (raw)
In-Reply-To: <20241212144244.601729511@linuxfoundation.org>
Hi Greg,
On 12/12/24 20:25, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.66 release.
> There are 356 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.
No problems seen on x86_64 and aarch64 with our testing.
Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Thanks,
Harshit
prev parent reply other threads:[~2024-12-14 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 14:55 Greg Kroah-Hartman
2024-12-12 21:51 ` Florian Fainelli
2024-12-13 1:41 ` Peter Schneider
2024-12-13 10:09 ` Jon Hunter
2024-12-13 10:17 ` Greg Kroah-Hartman
2024-12-13 13:18 ` Mark Brown
2024-12-13 14:49 ` Naresh Kamboju
2024-12-13 15:33 ` [PATCH 6.6] " Hardik Garg
2024-12-13 16:34 ` Hardik Garg
2024-12-13 16:51 ` [PATCH 6.6 000/356] " Shuah Khan
2024-12-13 18:51 ` SeongJae Park
2024-12-13 23:16 ` Ron Economos
2024-12-14 8:42 ` Muhammad Usama Anjum
2024-12-14 12:45 ` Harshit Mogalapalli [this message]
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=30e84dd5-bda1-461e-8401-c0c2177d6c57@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®