rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Alice Ryhl <aliceryhl@google.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	 Masami Hiramatsu <mhiramat@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	 rust-for-linux <rust-for-linux@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: linux-next: build failure after merge of the ftrace tree
Date: Sat, 9 Nov 2024 17:57:03 +0100	[thread overview]
Message-ID: <CANiq72ki5dR6rzBu5nxA0CRt9RpcbjJmoey82BCPLdxWHtWQLA@mail.gmail.com> (raw)
In-Reply-To: <3DC15367-3B1B-4808-988D-8C8D1CB2F4BB@goodmis.org>

On Sat, Nov 9, 2024 at 2:03 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> No, I'm currently traveling and thought your change just touched what's upstream.  I'll take it.

https://lore.kernel.org/linux-trace-kernel/20241109165520.1461400-1-ojeda@kernel.org/

Cheers,
Miguel

      reply	other threads:[~2024-11-09 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241108152149.28459a72@canb.auug.org.au>
     [not found] ` <20241108095933.72400ee1@gandalf.local.home>
2024-11-08 15:09   ` linux-next: build failure after merge of the ftrace tree Alice Ryhl
2024-11-08 20:35     ` Steven Rostedt
2024-11-08 21:05       ` Miguel Ojeda
2024-11-08 21:53         ` Miguel Ojeda
2024-11-09 11:09           ` Steven Rostedt
2024-11-09 11:55             ` Miguel Ojeda
2024-11-09 13:03               ` Steven Rostedt
2024-11-09 16:57                 ` Miguel Ojeda [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=CANiq72ki5dR6rzBu5nxA0CRt9RpcbjJmoey82BCPLdxWHtWQLA@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).