linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tools:bootconfig:scripts This file was missing the shebang line, so added it
Date: Thu, 24 Jul 2025 22:14:44 +0900	[thread overview]
Message-ID: <20250724221444.e59014b3cb0ab0123d6393d6@kernel.org> (raw)
In-Reply-To: <20250723235855.7e84eb3b5ed67975e1d16ca3@kernel.org>

On Wed, 23 Jul 2025 23:58:55 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> On Wed, 23 Jul 2025 04:23:01 +0530
> Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> 
> > This file was missing the shebang line, so added it.

BTW, I will change the title as

tools/bootconfig: scripts/ftrace.sh was missing the shebang line, so added it

Thanks,

> > 
> 
> Good catch :) 
> 
> Let me pick this.
> 
> Thanks!
> 
> > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> > ---
> >  tools/bootconfig/scripts/ftrace.sh | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/tools/bootconfig/scripts/ftrace.sh b/tools/bootconfig/scripts/ftrace.sh
> > index 186eed923041..cc5250c64699 100644
> > --- a/tools/bootconfig/scripts/ftrace.sh
> > +++ b/tools/bootconfig/scripts/ftrace.sh
> > @@ -1,3 +1,4 @@
> > +#!/bin/sh
> >  # SPDX-License-Identifier: GPL-2.0-only
> > 
> >  clear_trace() { # reset trace output
> > --
> > 2.49.1
> > 
> 
> 
> -- 
> Masami Hiramatsu (Google) <mhiramat@kernel.org>


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2025-07-24 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 22:53 [PATCH] tools:bootconfig:scripts This file was missing the shebang line, so added it Bhaskar Chowdhury
2025-07-23 14:58 ` Masami Hiramatsu
2025-07-24 13:14   ` Masami Hiramatsu [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=20250724221444.e59014b3cb0ab0123d6393d6@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=unixbhaskar@gmail.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;
as well as URLs for NNTP newsgroup(s).