From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@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
Subject: Re: [PATCH 5.4 000/123] 5.4.259-rc1 review
Date: Tue, 24 Oct 2023 10:28:40 +0200 [thread overview]
Message-ID: <2023102434-dreamless-parting-35ed@gregkh> (raw)
In-Reply-To: <eb759f41-db11-4f2e-b3a0-e9e92dea3196@linaro.org>
On Mon, Oct 23, 2023 at 09:53:08AM -0600, Daniel Díaz wrote:
> Same problems on Arm 32-bits as with 5.10 and 5.15:
>
> -----8<-----
> /builds/linux/drivers/gpio/gpio-vf610.c:249:11: error: use of undeclared identifier 'IRQCHIP_IMMUTABLE'
> 249 | .flags = IRQCHIP_IMMUTABLE | IRQCHIP_MASK_ON_SUSPEND
> | ^
> /builds/linux/drivers/gpio/gpio-vf610.c:250:6: error: use of undeclared identifier 'IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND'
> 250 | | IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND,
> | ^
> /builds/linux/drivers/gpio/gpio-vf610.c:251:2: error: use of undeclared identifier 'GPIOCHIP_IRQ_RESOURCE_HELPERS'
> 251 | GPIOCHIP_IRQ_RESOURCE_HELPERS,
> | ^
> /builds/linux/drivers/gpio/gpio-vf610.c:340:2: error: implicit declaration of function 'gpio_irq_chip_set_chip' [-Werror,-Wimplicit-function-declaration]
> 340 | gpio_irq_chip_set_chip(girq, &vf610_irqchip);
> | ^
> 4 errors generated.
> make[3]: *** [/builds/linux/scripts/Makefile.build:262: drivers/gpio/gpio-vf610.o] Error 1
> make[3]: Target '__build' not remade because of errors.
> make[2]: *** [/builds/linux/scripts/Makefile.build:497: drivers/gpio] Error 2
Now fixed up, thanks.
> /builds/linux/drivers/gpu/drm/drm_lock.c:363:6: warning: misleading indentation; statement is not part of the previous 'if' [-Wmisleading-indentation]
> 363 | */ mutex_lock(&dev->struct_mutex);
> | ^
> /builds/linux/drivers/gpu/drm/drm_lock.c:357:2: note: previous statement is here
> 357 | if (!drm_core_check_feature(dev, DRIVER_LEGACY))
> | ^
> 1 warning generated.
> ----->8-----
This can't be a new warning as no patches in this -rc touch this file,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-24 8:28 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
2023-10-23 15:53 ` Daniel Díaz
2023-10-24 8:28 ` Greg Kroah-Hartman [this message]
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=2023102434-dreamless-parting-35ed@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=daniel.diaz@linaro.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=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