From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.1 000/207] 6.1.4-rc1 review
Date: Fri, 6 Jan 2023 07:58:45 +0100 [thread overview]
Message-ID: <Y7fGpYyaJWym1BxW@kroah.com> (raw)
In-Reply-To: <Y7cmMKUr//oYKWXb@duo.ucw.cz>
On Thu, Jan 05, 2023 at 08:34:08PM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 6.1.4 release.
> > There are 207 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.
>
> Thank you.
>
> Is it known at this point if 6.1 will became next longterm release? It
> is not listed as such on https://www.kernel.org/category/releases.html
> . We might want to do some extra testing if it is.
A kernel can not become "long term" until it would have normally dropped
off of support. Right now there are known-regressions in 6.1 still that
are not resolved.
And "extra" testing is always good no matter what kernel branch it is
happening for, why not always do it?
thanks,
greg k-h
next prev parent reply other threads:[~2023-01-06 6:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 16:04 [PATCH 6.1 000/207] 6.1.4-rc1 review Greg Kroah-Hartman
2023-01-04 19:46 ` Allen Pais
2023-01-04 21:04 ` Florian Fainelli
2023-01-04 22:18 ` Shuah Khan
2023-01-05 0:21 ` Guenter Roeck
2023-01-05 7:02 ` Jon Hunter
2023-01-05 7:19 ` Bagas Sanjaya
2023-01-05 8:41 ` Naresh Kamboju
2023-01-05 11:13 ` Sudip Mukherjee (Codethink)
2023-01-05 11:23 ` Ron Economos
2023-01-05 14:43 ` Justin Forbes
2023-01-05 19:34 ` Pavel Machek
2023-01-06 6:58 ` Greg Kroah-Hartman [this message]
2023-01-06 23:53 ` Tyler Hicks
2023-01-07 7:13 ` Thorsten Leemhuis
2023-01-06 0:04 ` Rudi Heitbaum
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 17:17 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=Y7fGpYyaJWym1BxW@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.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 \
/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