public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: stable@vger.kernel.org, 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: Mon, 15 Jul 2024 13:43:21 +0200	[thread overview]
Message-ID: <2024071543-footing-vantage-bd4f@gregkh> (raw)
In-Reply-To: <07a7bc4b-9b71-486f-8666-d3b3593d682c@web.de>

On Fri, Jul 12, 2024 at 04:19:39PM +0200, Frank Scheiner wrote:
> On 12.07.24 15:32, Greg KH wrote:
> > I'm confused, which commit should we add, or should we just revert what
> > we have now?
> 
> Sorry for the confusion. Let me try again:
> 
> 1. 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
> 
> ...breaks the build for ia64, because it requires a header that does not
> exist before 8ff059b8531f3b98e14f0461859fc7cdd95823e4 for ia64.
> 
> 2. 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
> 
> adds this header and fixes the ia64 build, see for example [1].
> 
> [1]:
> https://github.com/linux-ia64/linux-stable-rc/actions/runs/9871144965#summary-27258970494
> 
> From my understanding 31e0721aeabde29371f624f56ce2f403508527a5 should
> not be merged w/o 8ff059b8531f3b98e14f0461859fc7cdd95823e4, which also
> seems to be the case for all other stable kernels from linux-5.12.y up.
> 
> So 8ff059b8531f3b98e14f0461859fc7cdd95823e4 should be added, too, if
> 31e0721aeabde29371f624f56ce2f403508527a5 stays in.

Ok, thanks, now queued up.

> > And I thought that ia64 was dead?
> 
> No, actually it's alive and well - just currently outside of mainline -
> but still in the stable kernels up to linux-6.6.y and for newer kernels
> patched back in. If you want to check on our CI ([2]), all current
> stable kernels build fine for ia64 and run in Ski - but linux-5.10.y
> currently only because I manually added
> 8ff059b8531f3b98e14f0461859fc7cdd95823e4 to the list of patches applied
> by the CI.
> 
> [2]: https://github.com/linux-ia64/linux-stable-rc/actions/runs/9901808825

Will be interesting to see how long it lasts, good luck!

greg k-h

  reply	other threads:[~2024-07-15 11:43 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
2024-07-12 13:32   ` Greg KH
2024-07-12 14:19     ` Frank Scheiner
2024-07-15 11:43       ` Greg KH [this message]
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=2024071543-footing-vantage-bd4f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frank.scheiner@web.de \
    --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