From: Greg KH <greg@kroah.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
ojeda@kernel.org, "Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: Patch "kbuild: rust: force `alloc` extern to allow "empty" Rust files" has been added to the 6.1-stable tree
Date: Wed, 19 Jun 2024 12:58:59 +0200 [thread overview]
Message-ID: <2024061948-zips-dividing-89c8@gregkh> (raw)
In-Reply-To: <CANiq72ma2Q1tvNboDyKOP+zOuefCW8Ooq_9cUx46MkFOG-8YRA@mail.gmail.com>
On Sun, Jun 16, 2024 at 12:38:41PM +0200, Miguel Ojeda wrote:
> On Sun, Jun 16, 2024 at 4:11 AM Sasha Levin <sashal@kernel.org> wrote:
> >
> > Cc: stable@vger.kernel.org # v6.6+
>
> This cannot be backported to 6.1 unless we upgrade the compiler, since
> the feature is not available in old versions.
>
> For future reference, this patch got picked for 6.1 a couple more times:
>
> https://lore.kernel.org/stable/CANiq72=V1=D-X5ncqN1pyfE4L1bz5zFRdBot6HpkCYie-EQnPA@mail.gmail.com/
> https://lore.kernel.org/stable/CANiq72ndLzts-KzUv_22vHF0tYkPvROv=oG+KP2KhbCvHkn60g@mail.gmail.com/
>
> If I had known it would cause your scripts to pick it up repeatedly,
> then I would have probably avoided `Fixes`/`Cc` -- it is a very minor
> issue.
Now dropped, sorry for the problems.
greg k-h
next prev parent reply other threads:[~2024-06-19 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240616021129.1681226-1-sashal@kernel.org>
2024-06-16 10:38 ` Patch "kbuild: rust: force `alloc` extern to allow "empty" Rust files" has been added to the 6.1-stable tree Miguel Ojeda
2024-06-19 10:58 ` Greg KH [this message]
[not found] <20240503164220.9073-1-sashal@kernel.org>
2024-05-03 17:10 ` Miguel Ojeda
2024-05-07 23:00 ` Sasha Levin
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=2024061948-zips-dividing-89c8@gregkh \
--to=greg@kroah.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wedsonaf@gmail.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 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.