public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: Apply e08ff622c91a to 6.6.y
Date: Thu, 8 Feb 2024 18:54:41 +0000	[thread overview]
Message-ID: <2024020833-flammable-default-afb2@gregkh> (raw)
In-Reply-To: <CANiq72mVfUT6VGcDqKGEEwNZo97pKq1roPMMk4qBvuq2tizwrQ@mail.gmail.com>

On Thu, Feb 08, 2024 at 07:29:13PM +0100, Miguel Ojeda wrote:
> Hi Greg, Sasha,
> 
> Please consider applying commit e08ff622c91a to 6.6.y. It requires the
> following chain:
> 
>     828176d037e2 ("rust: arc: add explicit `drop()` around `Box::from_raw()`")
>     ae6df65dabc3 ("rust: upgrade to Rust 1.72.1")
>     c61bcc278b19 ("rust: task: remove redundant explicit link")
>     a53d8cdd5a0a ("rust: print: use explicit link in documentation")
>     e08ff622c91a ("rust: upgrade to Rust 1.73.0")
> 
> which applies cleanly to 6.6.y. This upgrades the Rust compiler
> version from 1.71.1 to 1.73.0 (2 version upgrades + 3 prerequisites
> for the upgrades), fixing a couple issues with the Rust compiler
> version currently used in 6.6.y. In particular:
> 
>   - A build error with `CONFIG_RUST_DEBUG_ASSERTIONS` enabled
> (`.eh_frame` section unexpected generation). This is solved applying
> up to ae6df65dabc3.
> 
>   - A developer-only Make target error (building `.rsi` single-target
> files, i.e. the equivalent to requesting a preprocessed file in C).
> This is solved applying all of them.

All now queued up, thanks!

greg k-h

      reply	other threads:[~2024-02-08 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 18:29 Apply e08ff622c91a to 6.6.y Miguel Ojeda
2024-02-08 18:54 ` 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=2024020833-flammable-default-afb2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=sashal@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