All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: ojeda@kernel.org, aliceryhl@google.com,
	daniel.almeida@collabora.com, gary@garyguo.net,
	julian.stecklina@cyberus-technology.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] kbuild: rust: force `alloc` extern to allow "empty" Rust" failed to apply to 6.1-stable tree
Date: Mon, 29 Apr 2024 15:12:29 +0200	[thread overview]
Message-ID: <2024042951-coaster-parasail-a66c@gregkh> (raw)
In-Reply-To: <CANiq72nLGum-AqCW=xfHZ5fNw5xQ+Cnmab3VZ+NeHEN1tSNpzw@mail.gmail.com>

On Mon, Apr 29, 2024 at 02:22:13PM +0200, Miguel Ojeda wrote:
> On Mon, Apr 29, 2024 at 1:37 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > That was, but you also say:
> >         Fixes: 2f7ab1267dc9 ("Kbuild: add Rust support")
> > which is in 6.1, so what am I supposed to believe?
> >
> > Hence the email :)
> 
> Ah, I see. I thought the annotation "overrides" what could be found
> automatically via the `Fixes`.

When things are confusing, I punt and ask for what to do, especially
because people put commit ids in Fixes and don't always know how far
back those commits really were applied to.

thanks,

greg k-h

      parent reply	other threads:[~2024-04-29 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 11:21 FAILED: patch "[PATCH] kbuild: rust: force `alloc` extern to allow "empty" Rust" failed to apply to 6.1-stable tree gregkh
2024-04-29 11:25 ` Miguel Ojeda
2024-04-29 11:37   ` Greg KH
2024-04-29 12:22     ` Miguel Ojeda
2024-04-29 13:02       ` Miguel Ojeda
2024-04-29 13:12       ` 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=2024042951-coaster-parasail-a66c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aliceryhl@google.com \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=julian.stecklina@cyberus-technology.de \
    --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 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.