From: Steven Rostedt <rostedt@goodmis.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>, bpf <bpf@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
adubey@linux.ibm.com,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
KP Singh <kpsingh@chromium.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Florent Revest <revest@chromium.org>,
Puranjay Mohan <puranjay@kernel.org>
Subject: Re: Unsupported CONFIG_FPROBE and CONFIG_RETHOOK on ARM64
Date: Tue, 10 Sep 2024 21:32:41 -0400 [thread overview]
Message-ID: <20240910213241.58da3e43@gandalf.local.home> (raw)
In-Reply-To: <20240910212702.6679f507@gandalf.local.home>
On Tue, 10 Sep 2024 21:27:02 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > Does Linus have to be in CC to get any reply here? Come on, it's been
> > almost a full week.
Moral of the story is, if you had left out the above sentences, I would have
updated you nicely and this would not have been an issue.
-- Steve
next prev parent reply other threads:[~2024-09-11 1:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 1:02 Unsupported CONFIG_FPROBE and CONFIG_RETHOOK on ARM64 Andrii Nakryiko
2024-09-10 18:23 ` Andrii Nakryiko
2024-09-10 18:40 ` Steven Rostedt
2024-09-10 18:54 ` Steven Rostedt
2024-09-10 20:29 ` Andrii Nakryiko
2024-09-10 22:22 ` Steven Rostedt
2024-09-11 0:27 ` Andrii Nakryiko
2024-09-11 1:27 ` Steven Rostedt
2024-09-11 1:32 ` Steven Rostedt [this message]
2024-09-11 0:39 ` Masami Hiramatsu
2024-09-11 0:44 ` Andrii Nakryiko
2024-09-11 15:26 ` Masami Hiramatsu
2024-09-11 20:21 ` Andrii Nakryiko
2024-09-11 0:13 ` Masami Hiramatsu
2024-09-11 0:37 ` Andrii Nakryiko
2024-09-11 15:18 ` Masami Hiramatsu
2024-09-11 20:18 ` Andrii Nakryiko
2024-09-11 23:53 ` Masami Hiramatsu
2024-09-12 18:38 ` Andrii Nakryiko
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=20240910213241.58da3e43@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=adubey@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kpsingh@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=puranjay@kernel.org \
--cc=revest@chromium.org \
--cc=will@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