From: Sasha Levin <sashal@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: Consider applying patch to 6.12.y
Date: Mon, 2 Mar 2026 09:05:55 -0500 [thread overview]
Message-ID: <aaWZQ5JG4ndWDxov@laps> (raw)
In-Reply-To: <CANiq72mESZc2RfL2_5wt=LEg6M_7TZ__uELZ2tN=XGwB5Md_vg@mail.gmail.com>
On Mon, Mar 02, 2026 at 02:15:49AM +0100, Miguel Ojeda wrote:
>Hi Greg, Sasha,
>
>Sending this separately in case you don't track all replies to the
>`FAILED:` messages:
>
> https://lore.kernel.org/rust-for-linux/CANiq72nHESphKjW7uXm2D7HCNWNxmZ3nv+CSgrzEGgSKZ4_taA@mail.gmail.com/
>
>I am not sure why the patch failed to apply -- I would like to
>understand what happened there, in case I am missing something. I
>suspect something odd happened, since other of those `FAILED:`
>messages were strange too, i.e. most of them didn't seem to apply the
>`# ...` instructions, which is why most failed.
>
>But at least for that particular one, the patch should still be
>applied and it should have been cherry-pickable as far as I can tell:
>
> 0a9be83e57de ("rust: kbuild: pass `-Zunstable-options` for Rust 1.95.0")
>
>So if you cannot apply it, please let me know!
Hi Miguel,
It's already in the 6.12 tree. There's a quick explanation of what went wrong
with those queues (and caused the FAILED: spam) here:
https://lore.kernel.org/all/aaWWE5uQqz_eG69i@laps/ .
I'll spin up -rc2 with those missing commits.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-02 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 1:15 Consider applying patch to 6.12.y Miguel Ojeda
2026-03-02 14:05 ` Sasha Levin [this message]
2026-03-02 14:10 ` Miguel Ojeda
2026-03-02 14:12 ` Miguel Ojeda
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=aaWZQ5JG4ndWDxov@laps \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=miguel.ojeda.sandonis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.