linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/198] 6.1.21-rc1 review
Date: Tue, 21 Mar 2023 08:46:06 +0100	[thread overview]
Message-ID: <ZBlgvqscqTJLiCE4@kroah.com> (raw)
In-Reply-To: <20230321074819.2A17.409509F4@e16-tech.com>

On Tue, Mar 21, 2023 at 07:48:20AM +0800, Wang Yugui wrote:
> Hi,
> 
> 
> > This is the start of the stable review cycle for the 6.1.21 release.
> > There are 198 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, 22 Mar 2023 14:54:29 +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.21-rc1.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.21-rc1, but the panic does not
> happen on 6.1.20.
> 
> the patch *1 dropped in 6.1.9-rc is added to 6.1.21-rc1 again.
> *1 Subject: blk-mq: move the srcu_struct used for quiescing to the tagset
> 
> we need to drop it again, or need more patches.

Wow, I think this holds the record for the "patch that keeps getting
applied" :(

Sasha, can you add this one to your "never apply it" list for 6.1.y?

thanks,

greg k-h

  reply	other threads:[~2023-03-21  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 14:52 [PATCH 6.1 000/198] 6.1.21-rc1 review Greg Kroah-Hartman
2023-03-20 14:54 ` [PATCH 6.1 122/198] firmware: xilinx: dont make a sleepable memory allocation from an atomic context Greg Kroah-Hartman
2023-03-20 17:18 ` [PATCH 6.1 000/198] 6.1.21-rc1 review Chris Paterson
2023-03-20 18:42 ` Naresh Kamboju
2023-03-21  7:48   ` Greg Kroah-Hartman
2023-03-20 20:58 ` Florian Fainelli
2023-03-20 23:04 ` Shuah Khan
2023-03-20 23:48 ` Wang Yugui
2023-03-21  7:46   ` Greg Kroah-Hartman [this message]
2023-03-21  3:42 ` ogasawara takeshi
2023-03-21  4:48 ` Bagas Sanjaya
2023-03-21  8:42 ` Conor Dooley
2023-03-21 11:56 ` Jon Hunter

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=ZBlgvqscqTJLiCE4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).