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
Subject: Re: [PATCH 5.4 000/123] 5.4.259-rc1 review
Date: Tue, 24 Oct 2023 10:26:07 +0200 [thread overview]
Message-ID: <2023102452-tainted-mandolin-8c33@gregkh> (raw)
In-Reply-To: <5bd191c3-a58a-e6b4-12a6-64efb9b03f2e@roeck-us.net>
On Mon, Oct 23, 2023 at 07:36:25AM -0700, Guenter Roeck wrote:
> On 10/23/23 03:55, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.259 release.
> > There are 123 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, 25 Oct 2023 10:47:57 +0000.
> > Anything received after that time might be too late.
> >
>
> drivers/gpio/gpio-vf610.c:249:18: error: 'IRQCHIP_IMMUTABLE' undeclared here (not in a function); did you mean 'IS_IMMUTABLE'?
> 249 | .flags = IRQCHIP_IMMUTABLE | IRQCHIP_MASK_ON_SUSPEND
> | ^~~~~~~~~~~~~~~~~
> | IS_IMMUTABLE
> drivers/gpio/gpio-vf610.c:250:27: error: 'IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND' undeclared here (not in a function); did you mean 'IRQCHIP_MASK_ON_SUSPEND'?
> 250 | | IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | IRQCHIP_MASK_ON_SUSPEND
> drivers/gpio/gpio-vf610.c:251:9: error: 'GPIOCHIP_IRQ_RESOURCE_HELPERS' undeclared here (not in a function)
> 251 | GPIOCHIP_IRQ_RESOURCE_HELPERS,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/gpio/gpio-vf610.c:251:9: warning: excess elements in struct initializer
> drivers/gpio/gpio-vf610.c:251:9: note: (near initialization for 'vf610_irqchip')
> drivers/gpio/gpio-vf610.c: In function 'vf610_gpio_probe':
> drivers/gpio/gpio-vf610.c:340:9: error: implicit declaration of function 'gpio_irq_chip_set_chip'
>
> Also affects v5.10.y and v5.15.y.
Thanks, I'll go drop the offending patches from all of these trees now
and push out some -rc2 releases.
greg k-h
next prev parent reply other threads:[~2023-10-24 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 10:55 [PATCH 5.4 000/123] 5.4.259-rc1 review Greg Kroah-Hartman
2023-10-23 10:56 ` [PATCH 5.4 003/123] lib/test_meminit: fix off-by-one error in test_pages() Greg Kroah-Hartman
2023-10-23 14:36 ` [PATCH 5.4 000/123] 5.4.259-rc1 review Guenter Roeck
2023-10-24 8:26 ` Greg Kroah-Hartman [this message]
2023-10-23 15:53 ` Daniel Díaz
2023-10-24 8:28 ` Greg Kroah-Hartman
2023-10-23 18:38 ` Florian Fainelli
2023-10-24 8:56 ` Sudip Mukherjee (Codethink)
2023-10-25 18:57 ` 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=2023102452-tainted-mandolin-8c33@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox