From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever <cel@kernel.org>
Cc: stable@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 6.6.y 0/2] Apply commit 358de8b4f201 to 6.6.y
Date: Mon, 23 Jun 2025 08:33:48 +0200 [thread overview]
Message-ID: <2025062314-modular-robust-7b94@gregkh> (raw)
In-Reply-To: <20250617193853.388270-1-cel@kernel.org>
On Tue, Jun 17, 2025 at 03:38:51PM -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> Tested: "make binrpm-pkg" on Fedora 39 then installed with "rpm
> -ivh ...". Newly installed kernel reboots as expected.
>
> I will have a look at origin/linux-6.1.y next.
>
> Jose Ignacio Tornos Martinez (1):
> kbuild: rpm-pkg: simplify installkernel %post
>
> Masahiro Yamada (1):
> scripts: clean up IA-64 code
>
> scripts/checkstack.pl | 3 ---
> scripts/gdb/linux/tasks.py | 15 +++------------
> scripts/head-object-list.txt | 1 -
> scripts/kconfig/mconf.c | 2 +-
> scripts/kconfig/nconf.c | 2 +-
> scripts/package/kernel.spec | 28 +++++++++++-----------------
> scripts/package/mkdebian | 2 +-
> scripts/recordmcount.c | 1 -
> scripts/recordmcount.pl | 7 -------
> scripts/xz_wrap.sh | 1 -
> 10 files changed, 17 insertions(+), 45 deletions(-)
Why is this needed in 6.6.y? Is this just a new feature or fixing
something that has always been broken? It looks to me like a new
feature...
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-23 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:12 FAILED: patch "[PATCH] kbuild: rpm-pkg: simplify installkernel %post" failed to apply to 6.6-stable tree gregkh
2025-06-17 19:38 ` [PATCH 6.6.y 0/2] Apply commit 358de8b4f201 to 6.6.y Chuck Lever
2025-06-23 6:33 ` Greg KH [this message]
2025-06-23 13:21 ` Chuck Lever
2025-06-23 13:29 ` Chuck Lever
2025-06-17 19:38 ` [PATCH 6.6.y 1/2] scripts: clean up IA-64 code Chuck Lever
2025-06-19 9:04 ` Sasha Levin
2025-06-17 19:38 ` [PATCH 6.6.y 2/2] kbuild: rpm-pkg: simplify installkernel %post Chuck Lever
2025-06-19 9:04 ` Sasha Levin
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=2025062314-modular-robust-7b94@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=stable@vger.kernel.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