From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: stable@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
Samir M <samir@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Nicolas Schier <nsc@kernel.org>
Subject: Re: [PATCH 6.17.y] kbuild: Strip trailing padding bytes from modules.builtin.modinfo
Date: Tue, 11 Nov 2025 09:32:05 +0900 [thread overview]
Message-ID: <2025111149-hydration-moonlike-8f4e@gregkh> (raw)
In-Reply-To: <20251110223818.3951521-1-nathan@kernel.org>
On Mon, Nov 10, 2025 at 03:38:18PM -0700, Nathan Chancellor wrote:
> commit a26a6c93edfeee82cb73f55e87d995eea59ddfe8 upstream.
>
Oops, missed your backport, please ignore the FAILED email, I'll take
this now.
greg k-h
prev parent reply other threads:[~2025-11-11 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 1:51 FAILED: patch "[PATCH] kbuild: Strip trailing padding bytes from" failed to apply to 6.17-stable tree gregkh
2025-11-10 22:38 ` [PATCH 6.17.y] kbuild: Strip trailing padding bytes from modules.builtin.modinfo Nathan Chancellor
2025-11-11 0:32 ` Greg Kroah-Hartman [this message]
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=2025111149-hydration-moonlike-8f4e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=osandov@fb.com \
--cc=samir@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=venkat88@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).