From: Sven Joachim <svenjoac@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net,
rwarsow@gmx.de, conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 6.1 000/100] 6.1.74-rc1 review
Date: Thu, 18 Jan 2024 21:13:00 +0100 [thread overview]
Message-ID: <875xzqmmcz.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20240118104310.892180084@linuxfoundation.org> (Greg Kroah-Hartman's message of "Thu, 18 Jan 2024 11:48:08 +0100")
On 2024-01-18 11:48 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.74 release.
> There are 100 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.
Builds and works fine for me on x86_64.
Tested-by: Sven Joachim <svenjoac@gmx.de>
Cheers,
Sven
next prev parent reply other threads:[~2024-01-18 20:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:48 [PATCH 6.1 000/100] 6.1.74-rc1 review Greg Kroah-Hartman
2024-01-18 11:36 ` Pavel Machek
2024-01-18 18:35 ` SeongJae Park
2024-01-18 19:10 ` Florian Fainelli
2024-01-19 3:52 ` Naresh Kamboju
2024-01-19 5:40 ` Greg Kroah-Hartman
2024-01-19 16:07 ` Stefan Wiehler
2024-01-19 16:10 ` Greg Kroah-Hartman
2024-01-19 16:38 ` [PATCH] mips/smp: Call rcu_cpu_starting() earlier Stefan Wiehler
2024-01-20 6:38 ` Greg Kroah-Hartman
2024-01-21 16:52 ` Florian Fainelli
2024-01-22 17:07 ` Greg Kroah-Hartman
2024-01-18 20:13 ` Sven Joachim [this message]
2024-01-19 0:44 ` [PATCH 6.1 000/100] 6.1.74-rc1 review Shuah Khan
2024-01-19 1:05 ` Allen
2024-01-19 8:59 ` Yann Sionneau
2024-01-19 14:11 ` Jon Hunter
2024-01-20 0:46 ` Ron Economos
2024-01-20 2:18 ` Miguel Ojeda
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=875xzqmmcz.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 \
/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