From: "Shreeya Patel" <shreeya.patel@collabora.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.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, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
"Gustavo Padovan" <gustavo.padovan@collabora.com>,
"kernelci-regressions mailing list"
<kernelci-regressions@lists.collabora.co.uk>
Subject: Re: [PATCH 6.1 000/141] 6.1.88-rc1 review
Date: Thu, 25 Apr 2024 21:08:39 +0100 [thread overview]
Message-ID: <99cbe-662ab880-3-768c9e80@206940875> (raw)
In-Reply-To: <20240423213853.356988651@linuxfoundation.org>
On Wednesday, April 24, 2024 03:07 IST, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.1.88 release.
> There are 141 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 Thu, 25 Apr 2024 21:38:28 +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/v6.x/stable-review/patch-6.1.88-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-6.1.y
> and the diffstat can be found below.
>
KernelCI report for stable-rc/linux-6.1.y for this week :-
## stable-rc HEAD for linux-6.1.y:
Date: 2024-04-24
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=cde450ef0f2f55f2c1d63110616bc88f9af5cf38
## Build failures:
arm:
- multi_v7_defconfig (gcc-10) and omap2plus_defconfig (gcc-10)
- Build details :- https://linux.kernelci.org/build/stable-rc/branch/linux-6.1.y/kernel/v6.1.87-142-gcde450ef0f2f/
- Errors Summary
arch/arm/mach-omap2/pdata-quirks.c:271:2: error: implicit declaration of function ‘gpiod_add_lookup_table’ [-Werror=implicit-function-declaration]
arch/arm/mach-omap2/pdata-quirks.c:264:3: error: extra brace group at end of initializer
arch/arm/mach-omap2/pdata-quirks.c:262:41: error: ‘GPIO_ACTIVE_HIGH’ undeclared here (not in a function); did you mean ‘ACPI_ACTIVE_HIGH’?
arch/arm/mach-omap2/pdata-quirks.c:262:3: error: implicit declaration of function ‘GPIO_LOOKUP’; did you mean ‘IOP_LOOKUP’? [-Werror=implicit-function-declaration]
arch/arm/mach-omap2/pdata-quirks.c:261:3: error: ‘struct gpiod_lookup_table’ has no member named ‘table’
arch/arm/mach-omap2/pdata-quirks.c:261:11: error: extra brace group at end of initializer
arch/arm/mach-omap2/pdata-quirks.c:260:3: error: ‘struct gpiod_lookup_table’ has no member named ‘dev_id’
arch/arm/mach-omap2/pdata-quirks.c:259:34: error: storage size of ‘pandora_soc_audio_gpios’ isn’t known
arch/arm/mach-omap2/pdata-quirks.c:259:15: error: variable ‘pandora_soc_audio_gpios’ has initializer but incomplete type
## Boot failures:
No **new** boot failures seen for the stable-rc/linux-6.1.y commit head \o/
Tested-by: kernelci.org bot <bot@kernelci.org>
Thanks,
Shreeya Patel
next prev parent reply other threads:[~2024-04-25 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 21:37 Greg Kroah-Hartman
2024-04-23 23:00 ` SeongJae Park
2024-04-24 7:21 ` Pavel Machek
2024-04-24 8:23 ` Naresh Kamboju
2024-04-28 12:32 ` Vitaly Chikunov
2024-04-28 16:24 ` Guenter Roeck
2024-04-29 10:21 ` Greg Kroah-Hartman
2024-04-24 8:26 ` Ron Economos
2024-04-24 16:26 ` Florian Fainelli
2024-04-25 9:02 ` Jon Hunter
2024-04-25 9:03 ` Yann Sionneau
2024-04-25 19:27 ` Mateusz Jończyk
2024-04-25 20:08 ` Shreeya Patel [this message]
2024-04-26 2:21 ` Mark Brown
2024-04-26 10:44 ` Pavel Machek
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=99cbe-662ab880-3-768c9e80@206940875 \
--to=shreeya.patel@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.com \
--cc=jonathanh@nvidia.com \
--cc=kernelci-regressions@lists.collabora.co.uk \
--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
all inboxes | Powered by JetHome®