From: Frank Scheiner <frank.scheiner@web.de>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: akpm@linux-foundation.org, allen.lkml@gmail.com,
broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev, pavel@denx.de,
rwarsow@gmx.de, shuah@kernel.org, srw@sladewatkins.net,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
"Tomáš Glozar" <tglozar@gmail.com>
Subject: Re: [PATCH 5.10 000/284] 5.10.221-rc2 review
Date: Thu, 11 Jul 2024 12:56:44 +0200 [thread overview]
Message-ID: <76458f11-0ca4-4d3b-a9bc-916399f76b54@web.de> (raw)
In-Reply-To: <20240704094505.095988824@linuxfoundation.org>
Dear Greg, dear Sasha,
I noticed a build failure for linux-5.10.y for ia64 ([1]) (sorry,
actually since 5.10.221-rc1, but I didn't notice that build failure
before yesterday :-/ and as the review window for 5.10.222-rc1 is not
yet open, I thought I send it now as response to the last review window
announcement for 5.10.221-rc2):
https://github.com/linux-ia64/linux-stable-rc/actions/runs/9771252437/job/26974019958#step:8:3524:
```
[...]
CC [M] drivers/pps/pps.o
drivers/firmware/efi/memmap.c:16:10: fatal error: asm/efi.h: No such
file or directory
16 | #include <asm/efi.h>
| ^~~~~~~~~~~
compilation terminated.
[...]
```
[1]:
https://github.com/linux-ia64/linux-stable-rc/actions/runs/9771252437#summary-26974019958
This is related to the recent addition of this change set:
efi: memmap: Move manipulation routines into x86 arch tree
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.10.y&id=31e0721aeabde29371f624f56ce2f403508527a5
...to linux-5.10.y. For ia64 this change set on its own seems incomplete
as it requires a header not available for ia64 w/o additional changes.
Adding:
efi: ia64: move IA64-only declarations to new asm/efi.h header
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8ff059b8531f3b98e14f0461859fc7cdd95823e4
...or from here (according to GitHub this is in linux-stable(-rc)
starting with linux-5.12.y):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ff059b8531f3b98e14f0461859fc7cdd95823e4
fixes it for me with 5.10.222-rc1, see for example [2].
[2]:
https://github.com/linux-ia64/linux-stable-rc/actions/runs/9871144965#summary-27258970494
Cheers,
Frank
next prev parent reply other threads:[~2024-07-11 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 9:48 [PATCH 5.10 000/284] 5.10.221-rc2 review Greg Kroah-Hartman
2024-07-04 14:11 ` Jon Hunter
2024-07-04 14:28 ` Florian Fainelli
2024-07-05 5:16 ` Naresh Kamboju
2024-07-05 16:22 ` Nathan Chancellor
2024-07-07 10:35 ` Pavel Machek
2024-07-11 10:56 ` Frank Scheiner [this message]
2024-07-12 13:32 ` Greg KH
2024-07-12 14:19 ` Frank Scheiner
2024-07-15 11:43 ` Greg KH
2024-07-17 7:14 ` Frank Scheiner
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=76458f11-0ca4-4d3b-a9bc-916399f76b54@web.de \
--to=frank.scheiner@web.de \
--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=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=tglozar@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