From: Sasha Levin <sashal@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: stable@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
"Justin M. Forbes" <jforbes@fedoraproject.org>
Subject: Re: [PATCH 6.12.y] rust: kbuild: workaround `rustdoc` doctests modifier bug
Date: Mon, 10 Nov 2025 07:15:12 -0500 [thread overview]
Message-ID: <aRHXUKkqKMwn7xvX@laps> (raw)
In-Reply-To: <CANiq72m3Rv+L8P1J+JZu4LnR6YUKqssQu0G0yMQa51xCQWK+-w@mail.gmail.com>
On Sun, Nov 09, 2025 at 06:21:19PM +0100, Miguel Ojeda wrote:
>On Sat, Nov 8, 2025 at 3:03 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> [ added --remap-path-prefix comments missing in stable branch ]
>
>Do you mean you added the patch that added that workaround? Which branch?
>
>The resolution below does not show the comments, so I am confused. The
>resolution itself seems OK, but that line on the log plus not seeing
>the comments in the diff that are supposedly added somewhere else
>seems odd.
Sorry, it should have been s/added/removed - there's a comment upstream about
--remap-path-prefix that doesn't exist in the 6.12 tree.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-10 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 5:24 FAILED: patch "[PATCH] rust: kbuild: workaround `rustdoc` doctests modifier bug" failed to apply to 6.12-stable tree gregkh
2025-11-08 14:03 ` [PATCH 6.12.y] rust: kbuild: workaround `rustdoc` doctests modifier bug Sasha Levin
2025-11-09 17:21 ` Miguel Ojeda
2025-11-09 17:24 ` Miguel Ojeda
2025-11-10 12:15 ` Sasha Levin [this message]
2025-11-10 12:16 ` Miguel Ojeda
2025-11-09 17:28 ` FAILED: patch "[PATCH] rust: kbuild: workaround `rustdoc` doctests modifier bug" failed to apply to 6.12-stable tree 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=aRHXUKkqKMwn7xvX@laps \
--to=sashal@kernel.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