The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nicolas Schier <n.schier@avm.de>
To: Hu Haowen <2023002089@link.tyut.edu.cn>
Cc: gregkh@linuxfoundation.org, akpm@linux-foundation.org,
	masahiroy@kernel.org, ndesaulniers@google.com, ojeda@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scripts/show_delta: reformat code
Date: Fri, 1 Dec 2023 07:49:13 +0100	[thread overview]
Message-ID: <ZWmB67THrLcztb-3@buildd.core.avm.de> (raw)
In-Reply-To: <20231201053540.9534-1-2023002089@link.tyut.edu.cn>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On Fri, Dec 01, 2023 at 01:35:40PM +0800, Hu Haowen wrote:
> Correct some lines in irregular coding style to make them look more
> harmonious and fit the common coding regulations in Python.
> 
> Signed-off-by: Hu Haowen <2023002089@link.tyut.edu.cn>
> ---
>  scripts/show_delta | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/scripts/show_delta b/scripts/show_delta
> index 291ad65e3089..33446adce74b 100755
> --- a/scripts/show_delta
> +++ b/scripts/show_delta
> @@ -13,7 +13,7 @@ import sys
>  import string
>  
>  def usage():
> -	print ("""usage: show_delta [<options>] <filename>
> +	print("""usage: show_delta [<options>] <filename>

Hi,

thanks for your patch.  What Miguel already noticed for v1 is valid for
v2, too: there are still inconsistencies in the coding style, e.g.
`print (...)` and `print(...)`.

To simplify a consistent coding style for future work on the script,
using an external tool for reformatting (and mentioning it in the commit
message) would be helpful.  Miguel suggested Black or Ruff, I think this
is a good idea.

Kind regards,
Nicolas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-01  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  5:35 [PATCH v2] scripts/show_delta: reformat code Hu Haowen
2023-12-01  6:49 ` Nicolas Schier [this message]
2023-12-01 14:39   ` Hu Haowen
2023-12-01 15:32     ` Miguel Ojeda
2023-12-01  8:03 ` Greg KH

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=ZWmB67THrLcztb-3@buildd.core.avm.de \
    --to=n.schier@avm.de \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox