From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Yugui <wangyugui@e16-tech.com>
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
Subject: Re: [PATCH 6.1 000/313] 6.1.9-rc2 review
Date: Tue, 31 Jan 2023 08:24:45 +0100 [thread overview]
Message-ID: <Y9jCPZou887QFn/C@kroah.com> (raw)
In-Reply-To: <20230131104206.0E8A.409509F4@e16-tech.com>
On Tue, Jan 31, 2023 at 10:42:07AM +0800, Wang Yugui wrote:
> Hi,
>
>
> > This is the start of the stable review cycle for the 6.1.9 release.
> > There are 313 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 Wed, 01 Feb 2023 18:15:14 +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.9-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.
>
> fstests btrfs/056 triggered a panic for 6.1.9-rc2, but the panic does not happen
> on 6.1.8 and 6.2.0-rc4.
>
> reproduce frequency: 100%
Ick, yeah, the block patches got backported again. I'll drop them and
push out a -rc3, thanks for the report!
greg k-h
next prev parent reply other threads:[~2023-01-31 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:24 [PATCH 6.1 000/313] 6.1.9-rc2 review Greg Kroah-Hartman
2023-01-30 21:26 ` Conor Dooley
2023-01-30 22:57 ` Justin Forbes
2023-01-30 23:00 ` ogasawara takeshi
2023-01-31 2:42 ` Wang Yugui
2023-01-31 2:42 ` Wang Yugui
2023-01-31 7:24 ` Greg Kroah-Hartman [this message]
2023-01-31 3:12 ` Guenter Roeck
2023-01-31 3:21 ` Bagas Sanjaya
2023-01-31 11:49 ` Sudip Mukherjee
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 22:35 Walt Holman
2023-01-30 23:48 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=Y9jCPZou887QFn/C@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 \
--cc=wangyugui@e16-tech.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 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.