mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/9] Doing it for the consistency in the tree,eliminating the full path to the script
Date: Fri, 27 Jun 2025 14:07:07 -0500	[thread overview]
Message-ID: <be91d221-0182-44bf-8d70-131ed347b738@sabinyo.mountain> (raw)
In-Reply-To: <4ac24fc6d88cc4cc11ac6a4590562d23882deba6.1750459100.git.unixbhaskar@gmail.com>

On Sat, Jun 21, 2025 at 04:08:53AM +0530, Bhaskar Chowdhury wrote:
> Just try to making things consistent across the tree by eliminating full path
> to the script.
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
>  smatch_scripts/find_null_params.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/smatch_scripts/find_null_params.sh b/smatch_scripts/find_null_params.sh
> index 9e39146d2d40..a78eb7623fb4 100755
> --- a/smatch_scripts/find_null_params.sh
> +++ b/smatch_scripts/find_null_params.sh
> @@ -3,7 +3,7 @@
>  file=$1
> 
>  if [[ "$file" = "" ]] ; then
> -    echo "Usage:  $0 <file with smatch messages>"
> +	echo "Usage:  $(basename $0) <file with smatch messages>"

I don't love tab indents for bash scripts.  I know that the kernel does
this for scripts but I don't love it there either.  So I've been hand
editing these patches.  It's easy for me to hand edit these in my email
client so no worries.

>      exit 1
>  fi
> 
> @@ -13,7 +13,7 @@ cat null_calls.txt unchecked | sort | uniq -d > null_params.txt
>  IFS="
>  "
>  for i in $(cat null_params.txt) ; do
> -	grep "$i" $file | grep -w undefined
> +	grep "$i" $file | grep -w undefined

In this case I think you were removing a space from the end of the line
but somehow your email client seems to have deleted it so the patch
didn't apply.  I did this manually as well, but you may want to fix that.

Anyway, all of these are applied now.

regards,
dan carpenter


  reply	other threads:[~2025-06-27 19:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 22:38 [PATCH 0/9] Trivial fixes in the smatch tree Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 1/9] Replace pipes with a binary for cpu core count Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 2/9] Looks nicer in usage output without the full path of the script Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 3/9] Eliminate the full path to the script in usage output Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 4/9] Doing it for the consistency in the tree,eliminating the full path to the script Bhaskar Chowdhury
2025-06-27 19:07   ` Dan Carpenter [this message]
2025-06-20 22:38 ` [PATCH 5/9] Again, for the consistency, eliminate " Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 6/9] Trivial fixup to take away the full path of " Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 7/9] Took away the full path to " Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 8/9] Usage shows without " Bhaskar Chowdhury
2025-06-20 22:38 ` [PATCH 9/9] Trivial changes,usage text show scriptname without path,and few of them use nproc binary to show cpu core Bhaskar Chowdhury

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=be91d221-0182-44bf-8d70-131ed347b738@sabinyo.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=linux-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

all inboxes | Powered by JetHome®