All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jackie Liu <liu.yun@linux.dev>,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Propagate errors from remote event bulk updates
Date: Thu, 16 Jul 2026 08:55:30 +0100	[thread overview]
Message-ID: <aliOcliJWcruun2z@google.com> (raw)
In-Reply-To: <20260715141956.6baf0134@gandalf.local.home>

On Wed, Jul 15, 2026 at 02:19:56PM -0400, Steven Rostedt wrote:
> On Wed, 15 Jul 2026 08:25:09 +0100
> Vincent Donnefort <vdonnefort@google.com> wrote:
> 
> > > I checked the v2 series. Patch 02/18 handles registration failure cleanup,
> > > and patch 03/18 changes the boolean parsing in
> > > remote_events_dir_enable_write(), but the loop still ignores errors from
> > > trace_remote_enable_event().
> > > 
> > > Would you prefer this fix to be folded into your series, or should I resend
> > > a v2 rebased on top of it?  
> > 
> > Ha yes my bad. Then no, no need to send it separately. 
> 
> So should I take this patch and send it to Linus now?

There's a v2 here [1] with my Reviewed-by tag.

[1] https://lore.kernel.org/all/20260715074455.3897-1-liu.yun@linux.dev/

> 
> -- Steve

      reply	other threads:[~2026-07-16  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  6:04 [PATCH] tracing: Propagate errors from remote event bulk updates Jackie Liu
2026-07-15  6:44 ` Vincent Donnefort
2026-07-15  7:02   ` Jackie Liu
2026-07-15  7:25     ` Vincent Donnefort
2026-07-15 18:19       ` Steven Rostedt
2026-07-16  7:55         ` Vincent Donnefort [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=aliOcliJWcruun2z@google.com \
    --to=vdonnefort@google.com \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=liu.yun@linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.