From: Steven Rostedt <rostedt@goodmis.org>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, linux-um@lists.infradead.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Andy Lutomirski <luto@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 2/3] compiler: inline does not imply notrace
Date: Fri, 26 May 2023 05:40:18 +0000 [thread overview]
Message-ID: <20230526014018.5ebafc55@rorschach.local.home> (raw)
In-Reply-To: <D4B1FB24-C351-411B-8A40-4DAFE95FA921@gmail.com>
On Thu, 25 May 2023 22:17:33 -0700
Nadav Amit <nadav.amit@gmail.com> wrote:
> Ugh. If you cc’d me, I wouldn’t bother you during your vacation. :)
Oh, and if you are interested in tracing patches, just subscribe to
linux-trace-kernel@vger.kernel.org.
-- Steve
next prev parent reply other threads:[~2023-05-26 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 21:00 [PATCH v2 0/3] kprobes: notrace enhancements Nadav Amit
2023-05-25 21:00 ` [PATCH v2 1/3] kprobes: Mark descendents of core_kernel_text as notrace Nadav Amit
2023-05-25 21:00 ` [PATCH v2 2/3] compiler: inline does not imply notrace Nadav Amit
2023-05-26 2:28 ` Steven Rostedt
2023-05-26 5:17 ` Nadav Amit
2023-05-26 5:35 ` Steven Rostedt
2023-05-26 5:40 ` Steven Rostedt [this message]
2023-05-25 21:00 ` [PATCH v2 3/3] lib: Allow traceing of usercopy, xarray, iov_iter, find_bit Nadav Amit
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=20230526014018.5ebafc55@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).