public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.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, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Vineeth Vijayan <vneethv@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	linux-s390@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: [PATCH 5.15 000/276] 5.15.195-rc1 review
Date: Sun, 19 Oct 2025 13:58:25 +0200	[thread overview]
Message-ID: <2025101906-spinner-neutron-0a9a@gregkh> (raw)
In-Reply-To: <CA+G9fYvRHXOJUfKqxj9MNA1ax1i2xCrazh0x9b3QvrXLm+N+qQ@mail.gmail.com>

On Sat, Oct 18, 2025 at 02:38:46PM +0530, Naresh Kamboju wrote:
> On Fri, 17 Oct 2025 at 21:16, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.195 release.
> > There are 276 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 Sun, 19 Oct 2025 14:50:59 +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/v5.x/stable-review/patch-5.15.195-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-5.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> The S390 build failed on stable-rc 5.15.195-rc1 with gcc-12, gcc-8
> and clang-21 due to following build warnings / errors.
> 
> ### Build error:
> drivers/s390/cio/device.c: In function 'purge_fn':
> drivers/s390/cio/device.c:1330:23: error: passing argument 1 of
> 'spin_lock_irq' from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>  1330 |         spin_lock_irq(&sch->lock);
>       |                       ^~~~~~~~~~
>       |                       |
>       |                       spinlock_t ** {aka struct spinlock **}
> In file included from drivers/s390/cio/device.c:16:
> include/linux/spinlock.h:387:55: note: expected 'spinlock_t *' {aka
> 'struct spinlock *'} but argument is of type 'spinlock_t **' {aka
> 'struct spinlock **'}
>   387 | static __always_inline void spin_lock_irq(spinlock_t *lock)
>       |                                           ~~~~~~~~~~~~^~~~
> drivers/s390/cio/device.c:1353:25: error: passing argument 1 of
> 'spin_unlock_irq' from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>  1353 |         spin_unlock_irq(&sch->lock);
>       |                         ^~~~~~~~~~
>       |                         |
>       |                         spinlock_t ** {aka struct spinlock **}
> include/linux/spinlock.h:412:57: note: expected 'spinlock_t *' {aka
> 'struct spinlock *'} but argument is of type 'spinlock_t **' {aka
> 'struct spinlock **'}
>   412 | static __always_inline void spin_unlock_irq(spinlock_t *lock)
>       |                                             ~~~~~~~~~~~~^~~~
> cc1: some warnings being treated as errors
> make[3]: *** [scripts/Makefile.build:289: drivers/s390/cio/device.o] Error 1
> 
> ### Suspecting patches
> Suspecting commit,
> 
>   s390/cio: Update purge function to unregister the unused subchannels
>   [ Upstream commit 9daa5a8795865f9a3c93d8d1066785b07ded6073 ]
> 
> 
> Build regressions: 5.15.195-rc1: S390: cio/device.c:1330:23: error:
> passing argument 1 of 'spin_lock_irq' from incompatible pointer type
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Thanks for the report, I'll go drop this from all 3 queues now.

greg k-h

      reply	other threads:[~2025-10-19 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251017145142.382145055@linuxfoundation.org>
2025-10-18  9:08 ` [PATCH 5.15 000/276] 5.15.195-rc1 review Naresh Kamboju
2025-10-19 11:58   ` Greg Kroah-Hartman [this message]

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=2025101906-spinner-neutron-0a9a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=benjamin.copeland@linaro.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=hca@linux.ibm.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=oberpar@linux.ibm.com \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vneethv@linux.ibm.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