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,
"kernelci-regressions mailing list"
<kernelci-regressions@lists.collabora.co.uk>,
"Gustavo Padovan" <padovan@collabora.com>
Subject: Re: [PATCH 6.6 000/192] 6.6.36-rc1 review
Date: Wed, 26 Jun 2024 11:38:28 +0100 [thread overview]
Message-ID: <30762b-667bef80-5-529d9000@215728945> (raw)
In-Reply-To: <20240625085537.150087723@linuxfoundation.org>
On Tuesday, June 25, 2024 15:01 IST, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.6.36 release.
> There are 192 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, 27 Jun 2024 08:54:55 +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.6.36-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.6.y
> and the diffstat can be found below.
>
KernelCI report for stable-rc/linux-6.6.y for this week :-
Date: 2024-06-25
## Build failures:
arm:
- multi_v7_defconfig (gcc-10)
- Build details :-
http://localhost:3000/goto/RvP98cQIg?orgId=1
- Errors :-
arm-linux-gnueabihf-ld: drivers/firmware/efi/efi-init.o: in function `.LANCHOR1':
efi-init.c:(.data+0x0): multiple definition of `screen_info'; arch/arm/kernel/setup.o:setup.c:(.data+0x12c): first defined here
Tested-by: kernelci.org bot <bot@kernelci.org>
Thanks,
Shreeya Patel
next prev parent reply other threads:[~2024-06-26 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 9:31 [PATCH 6.6 000/192] 6.6.36-rc1 review Greg Kroah-Hartman
2024-06-25 11:09 ` Naresh Kamboju
2024-06-25 14:43 ` Naresh Kamboju
2024-06-25 15:08 ` Arnd Bergmann
2024-06-27 11:28 ` Greg Kroah-Hartman
2024-06-26 8:04 ` Jon Hunter
2024-06-25 11:41 ` Florian Fainelli
2024-06-25 13:30 ` Peter Schneider
2024-06-25 13:49 ` Takeshi Ogasawara
2024-06-25 17:03 ` SeongJae Park
2024-06-25 21:25 ` Shuah Khan
2024-06-26 10:38 ` Shreeya Patel [this message]
2024-06-26 12:48 ` Ron Economos
2024-06-26 20:56 ` Naresh Kamboju
2024-06-27 3:35 ` Kelsey Steele
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=30762b-667bef80-5-529d9000@215728945 \
--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=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=padovan@collabora.com \
--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