From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Colin Ian King <colin.i.king@gmail.com>,
Jeff Xie <jeff.xie@linux.dev>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Justin Stitt <justinstitt@google.com>,
Levi Yun <yeoreum.yun@arm.com>,
Li Chen <chenl311@chinatelecom.cn>,
Ryan Roberts <ryan.roberts@arm.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tatsuya S <tatsuya.s2862@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>,
Zheng Yejian <zhengyejian@huaweicloud.com>,
guoweikang <guoweikang.kernel@gmail.com>
Subject: Re: [GIT PULL] tracing: Updates for v6.13
Date: Fri, 22 Nov 2024 17:13:38 -0500 [thread overview]
Message-ID: <5f8d128b-9007-4eff-bf98-e56603469130@efficios.com> (raw)
In-Reply-To: <20241122170057.051b754f@gandalf.local.home>
On 2024-11-22 17:00, Steven Rostedt wrote:
> On Fri, 22 Nov 2024 13:54:49 -0800
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> I have pulled this, but I expect this horror to be fixed.
>
> Thanks.
>
> Mathieu,
>
> Care to send a patch to address Linus's concerns.
Sure, I will prepare a fix.
Linus's concerns are clearly expressed and I missed that they applied
to __DO_TRACE() as well the last time.
Sorry about that!
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2024-11-22 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 2:45 Steven Rostedt
2024-11-22 21:54 ` Linus Torvalds
2024-11-22 22:00 ` Steven Rostedt
2024-11-22 22:13 ` Mathieu Desnoyers [this message]
2024-11-22 22:13 ` Steven Rostedt
2024-11-22 22:30 ` Linus Torvalds
2024-11-22 22:41 ` Steven Rostedt
2024-11-22 22:32 ` pr-tracker-bot
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=5f8d128b-9007-4eff-bf98-e56603469130@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=andrii@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=chenl311@chinatelecom.cn \
--cc=colin.i.king@gmail.com \
--cc=guoweikang.kernel@gmail.com \
--cc=jeff.xie@linux.dev \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=tatsuya.s2862@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=yeoreum.yun@arm.com \
--cc=zhengyejian@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®