From: Jaewon Jung <jaewon8868@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Keep copying markers when one instance is stopped
Date: Wed, 4 Nov 2026 15:35:38 +0900 [thread overview]
Message-ID: <20261104063552.28094-1-jaewon8868@gmail.com> (raw)
In-Reply-To: <20261103095019.6a88e783@gandalf.local.home>
The copy_trace_marker documentation says:
> If no instance has this option set, then a write will error with
> the errno of ENODEV.
With global copying disabled and another instance enabled, both versions
record the marker in that instance, but the proposed change returns
-ENODEV.
This seems inconsistent with the documentation. Should we return the
last write's result, as in v2?
next prev parent reply other threads:[~2026-11-04 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 0:44 [PATCH v2] tracing: Keep copying markers when one instance is stopped Jaewon Jung
2026-11-03 1:05 ` sashiko-bot
2026-11-03 14:50 ` Steven Rostedt
2026-11-04 6:35 ` Jaewon Jung [this message]
2026-11-04 13:57 ` Steven Rostedt
2026-11-04 23:19 ` [PATCH v3] " Jaewon Jung
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=20261104063552.28094-1-jaewon8868@gmail.com \
--to=jaewon8868@gmail.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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