All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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 5.10 000/187] 5.10.202-rc3 review
Date: Mon, 27 Nov 2023 12:40:51 +0000	[thread overview]
Message-ID: <2023112745-spree-require-c3a6@gregkh> (raw)
In-Reply-To: <76363981-1f2a-47c2-b1b1-ae039844e936@roeck-us.net>

On Sun, Nov 26, 2023 at 10:23:24AM -0800, Guenter Roeck wrote:
> On 11/26/23 07:46, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.202 release.
> > There are 187 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 Tue, 28 Nov 2023 15:43:06 +0000.
> > Anything received after that time might be too late.
> > 
> 
> For v5.10.201-188-g2f84e268b78b (5.10.202-rc3):
> 
> s390:defconfig, s390:allmodconfig, s390:debug_defconfig:
> 
> drivers/s390/crypto/ap_bus.c: In function 'ap_bus_force_rescan':
> drivers/s390/crypto/ap_bus.c:791:28: error: 'ap_scan_bus_count' undeclared
> 
> $ git grep ap_scan_bus_count
> drivers/s390/crypto/ap_bus.c:   if (atomic64_read(&ap_scan_bus_count) <= 0)
> $ git blame drivers/s390/crypto/ap_bus.c |& grep ap_scan_bus_count
> 467f51fb3ab6e (Harald Freudenberger 2023-10-23 09:57:10 +0200  791) 	if (atomic64_read(&ap_scan_bus_count) <= 0)
> 
> which is:
> 
> 467f51fb3ab6 s390/ap: fix AP bus crash on early config change callback invocation

Now dropped, thanks.

greg k-h

  reply	other threads:[~2023-11-27 12:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 15:46 [PATCH 5.10 000/187] 5.10.202-rc3 review Greg Kroah-Hartman
2023-11-26 16:22 ` Guenter Roeck
2023-11-27 11:45   ` [PATCH 5.10] interconnect: qcom: Add support for mask-based BCMs djakov
2023-11-27 12:40     ` Greg KH
2023-11-26 18:23 ` [PATCH 5.10 000/187] 5.10.202-rc3 review Guenter Roeck
2023-11-27 12:40   ` Greg Kroah-Hartman [this message]
2023-11-27  3:51 ` Florian Fainelli
2023-11-27 21:25 ` Pavel Machek
2023-11-28  6:56   ` Dominique Martinet
2023-11-28 20:43     ` Pavel Machek
2023-11-28 10:42   ` Richard Fitzgerald
2023-11-28 20:40     ` Pavel Machek
2023-11-29 11:35       ` Richard Fitzgerald
2023-11-27 23:27 ` Jon Hunter
2023-11-27 23:37   ` Jon Hunter
2023-11-28  9:42     ` Greg Kroah-Hartman
2023-11-28  2:52 ` Guenter Roeck
2023-11-28  9:30 ` Naresh Kamboju

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=2023112745-spree-require-c3a6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.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 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.