public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/198] 6.18.24-rc1 review
Date: Tue, 21 Apr 2026 17:02:30 +0200	[thread overview]
Message-ID: <2026042122-refurnish-silliness-47f1@gregkh> (raw)
In-Reply-To: <67def94b-6ed0-4000-be08-314f30c7a923@sirena.org.uk>

On Tue, Apr 21, 2026 at 03:04:33PM +0100, Mark Brown wrote:
> On Mon, Apr 20, 2026 at 05:39:39PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.18.24 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.
> 
> This doesn't build for arm multi_v5_defconfig or bcm2835_defconfig:
> 
> In file included from /build/stage/linux/include/linux/srcu.h:59,
>                  from /build/stage/linux/include/linux/notifier.h:16,
>                  from /build/stage/linux/include/linux/memory_hotplug.h:7,
>                  from /build/stage/linux/include/linux/mmzone.h:1538,
>                  from /build/stage/linux/include/linux/gfp.h:7,
>                  from /build/stage/linux/include/linux/mm.h:7,
>                  from /build/stage/linux/arch/arm/kernel/asm-offsets.c:14:
> /build/stage/linux/include/linux/srcutiny.h:14:10: fatal error: linux/irq_work_t
> ypes.h: No such file or directory
>    14 | #include <linux/irq_work_types.h>
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~


I'll go drop the offending commit,t hanks.

greg k-h

  reply	other threads:[~2026-04-21 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 15:39 [PATCH 6.18 000/198] 6.18.24-rc1 review Greg Kroah-Hartman
2026-04-20 17:29 ` Florian Fainelli
2026-04-20 21:11 ` Peter Schneider
2026-04-21  7:04 ` Ron Economos
2026-04-21  8:08 ` Brett A C Sheffield
2026-04-21  9:55 ` Miguel Ojeda
2026-04-21 15:02   ` Greg KH
2026-04-21 11:16 ` Wentao Guan
2026-04-21 14:04 ` Mark Brown
2026-04-21 15:02   ` Greg Kroah-Hartman [this message]
2026-04-21 15:37 ` Dileep malepu
2026-04-21 16:55 ` Shuah Khan

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=2026042122-refurnish-silliness-47f1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.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@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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