From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: ojeda@kernel.org, aliceryhl@google.com,
jforbes@fedoraproject.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] rust: kbuild: treat `build_error` and `rustdoc` as kernel" failed to apply to 6.12-stable tree
Date: Wed, 12 Nov 2025 09:57:38 +0900 [thread overview]
Message-ID: <2025111242-unchanged-catwalk-49f0@gregkh> (raw)
In-Reply-To: <CANiq72kEW52FBsanY2eqs+OXS6xLx6+J052RTBzFLdR5dinNuQ@mail.gmail.com>
On Tue, Nov 11, 2025 at 01:46:20PM +0100, Miguel Ojeda wrote:
> On Sun, Nov 9, 2025 at 6:05 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
> >
> > Sasha's sibling resolution looks fine, thanks!
>
> Just in case this was missed, I think this one and the related one
> weren't picked up for 6.12.58-rc2.
>
> Should I do something?
No, I just didn't get the chance to pick up backports for 6.12 and older
just yet, I wanted to push out what we had already. My queue is big,
due to travel at the moment, sorry.
greg "what day/timezone/continent is it now?" k-h
prev parent reply other threads:[~2025-11-12 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 5:24 FAILED: patch "[PATCH] rust: kbuild: treat `build_error` and `rustdoc` as kernel" failed to apply to 6.12-stable tree gregkh
2025-11-08 14:07 ` [PATCH 6.12.y] rust: kbuild: treat `build_error` and `rustdoc` as kernel objects Sasha Levin
2025-11-09 17:05 ` FAILED: patch "[PATCH] rust: kbuild: treat `build_error` and `rustdoc` as kernel" failed to apply to 6.12-stable tree Miguel Ojeda
2025-11-11 12:46 ` Miguel Ojeda
2025-11-12 0:57 ` Greg KH [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=2025111242-unchanged-catwalk-49f0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=jforbes@fedoraproject.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--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