All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-trace-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: tracing: Cleanup event_enable_trigger_parse() by using __free()
Date: Fri, 3 Jul 2026 15:33:41 -0400	[thread overview]
Message-ID: <20260703153341.0b2117fe@gandalf.local.home> (raw)
In-Reply-To: <bc9627b8-90fe-42f4-82f1-541bd96866aa@web.de>

On Fri, 3 Jul 2026 21:20:46 +0200
Markus Elfring <Markus.Elfring@web.de> wrote:

> > That example uses the variable in a specific block whereas this variable is
> > used in most of the function, which makes it appropriate where it lies.  
> 
> What does hinder you to apply scope reductions for selected local variables
> more often?
> 

OK, now you are just talking like Eliza.

-- Steve

  reply	other threads:[~2026-07-03 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 21:48 [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free() Steven Rostedt
2026-07-01 22:41 ` Masami Hiramatsu
2026-07-02  9:58 ` Markus Elfring
2026-07-02 20:53   ` Steven Rostedt
2026-07-03  5:00     ` Markus Elfring
2026-07-03 15:42       ` Steven Rostedt
2026-07-03 18:37         ` Markus Elfring
2026-07-03 19:09           ` Steven Rostedt
2026-07-03 19:20             ` Markus Elfring
2026-07-03 19:33               ` Steven Rostedt [this message]
2026-07-02 11:58 ` [PATCH] " Markus Elfring

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=20260703153341.0b2117fe@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=Markus.Elfring@web.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@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 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.