Skip to contentSkip to conversation

streamline_config.pl: Fix Perl spacing

PATCH Applied Steven Rostedt 3 participants 11 messages Mar 22, 2021 – Mar 26, 2021

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

cover streamline_config.pl: Fix Perl spacing

Talking with John Hawley about how vim and emacs deal with Perl files with respect to tabs and spaces, I found that some of my Perl code in the kernel had inconsistent spacing. The way emacs handles Perl by default is to use 4 spaces per indent, but make all 8 spaces into a single tab. Vim does not do this by default. But if you add the vim variable control:

# vim: softtabstop=4

to a perl file, it makes vim behave the same way as emacs.

The first patch is to change all 8 spaces into a single tab (mostly from people editing the file with vim). The next patch adds the softtabstop variable to make vim act like emacs by default.

Steven Rostedt (VMware) (2):
streamline_config.pl: Make spacing consistent streamline_config.pl: Add softtabstop=4 for vim users

----

 scripts/kconfig/streamline_config.pl | 80 ++++++++++++++++++------------------
 1 file changed, 41 insertions(+), 39 deletions(-)
#1 lore raw

PATCH 1/2 streamline_config.pl: Make spacing consistent

From: "Steven Rostedt (VMware)" <[email protected]>

As Perl code tends to have 4 space indentation, but uses tabs for every 8 spaces, make that consistent in the streamline_config.pl code. Replace all 8 spaces with a single tab.

---
 scripts/kconfig/streamline_config.pl | 78 ++++++++++++++--------------
 1 file changed, 39 insertions(+), 39 deletions(-)
scripts/kconfig/streamline_config.pl +39 -39
index 1c78ba49ca99..059061b6daef 100755
@@ -601,12 +601,12 @@ if (defined($ENV{'LMC_KEEP'})) {
 sub in_preserved_kconfigs {
     my $kconfig = $config2kfile{$_[0]};
     if (!defined($kconfig)) {
-        return 0;
+	return 0;
     }
     foreach my $excl (@preserved_kconfigs) {
-        if($kconfig =~ /^$excl/) {
-            return 1;
-        }
+	if($kconfig =~ /^$excl/) {
+	    return 1;
+	}
     }
     return 0;
 }
@@ -629,52 +629,52 @@ foreach my $line (@config_file) {
     }
 
     if (/CONFIG_MODULE_SIG_KEY="(.+)"/) {
-        my $orig_cert = $1;
-        my $default_cert = "certs/signing_key.pem";
-
-        # Check that the logic in this script still matches the one in Kconfig
-        if (!defined($depends{"MODULE_SIG_KEY"}) ||
-            $depends{"MODULE_SIG_KEY"} !~ /"\Q$default_cert\E"/) {
-            print STDERR "WARNING: MODULE_SIG_KEY assertion failure, ",
-                "update needed to ", __FILE__, " line ", __LINE__, "\n";
-            print;
-        } elsif ($orig_cert ne $default_cert && ! -f $orig_cert) {
-            print STDERR "Module signature verification enabled but ",
-                "module signing key \"$orig_cert\" not found. Resetting ",
-                "signing key to default value.\n";
-            print "CONFIG_MODULE_SIG_KEY=\"$default_cert\"\n";
-        } else {
-            print;
-        }
-        next;
+	my $orig_cert = $1;
+	my $default_cert = "certs/signing_key.pem";
+
+	# Check that the logic in this script still matches the one in Kconfig
+	if (!defined($depends{"MODULE_SIG_KEY"}) ||
+	    $depends{"MODULE_SIG_KEY"} !~ /"\Q$default_cert\E"/) {
+	    print STDERR "WARNING: MODULE_SIG_KEY assertion failure, ",
+		"update needed to ", __FILE__, " line ", __LINE__, "\n";
+	    print;
+	} elsif ($orig_cert ne $default_cert && ! -f $orig_cert) {
+	    print STDERR "Module signature verification enabled but ",
+		"module signing key \"$orig_cert\" not found. Resetting ",
+		"signing key to default value.\n";
+	    print "CONFIG_MODULE_SIG_KEY=\"$default_cert\"\n";
+	} else {
+	    print;
+	}
+	next;
     }
 
     if (/CONFIG_SYSTEM_TRUSTED_KEYS="(.+)"/) {
-        my $orig_keys = $1;
-
-        if (! -f $orig_keys) {
-            print STDERR "System keyring enabled but keys \"$orig_keys\" ",
-                "not found. Resetting keys to default value.\n";
-            print "CONFIG_SYSTEM_TRUSTED_KEYS=\"\"\n";
-        } else {
-            print;
-        }
-        next;
+	my $orig_keys = $1;
+
+	if (! -f $orig_keys) {
+	    print STDERR "System keyring enabled but keys \"$orig_keys\" ",
+		"not found. Resetting keys to default value.\n";
+	    print "CONFIG_SYSTEM_TRUSTED_KEYS=\"\"\n";
+	} else {
+	    print;
+	}
+	next;
     }
 
     if (/^(CONFIG.*)=(m|y)/) {
-        if (in_preserved_kconfigs($1)) {
-            dprint "Preserve config $1";
-            print;
-            next;
-        }
+	if (in_preserved_kconfigs($1)) {
+	    dprint "Preserve config $1";
+	    print;
+	    next;
+	}
 	if (defined($configs{$1})) {
 	    if ($localyesconfig) {
-	        $setconfigs{$1} = 'y';
+		$setconfigs{$1} = 'y';
 		print "$1=y\n";
 		next;
 	    } else {
-	        $setconfigs{$1} = $2;
+		$setconfigs{$1} = $2;
 	    }
 	} elsif ($2 eq "m") {
 	    print "# $1 is not set\n";
Signature · 1 line
2.30.1
#2 lore raw

PATCH 2/2 streamline_config.pl: Add softtabstop=4 for vim users

In reply to Steven Rostedt

From: "Steven Rostedt (VMware)" <[email protected]>

The tab stop for Perl files is by default (at least in emacs) to be 4 spaces, where a tab is used for all 8 spaces. Add a local variable comment to make vim do the same by default, and this will help keep the file consistent in the future when others edit it via vim and not emacs.

---
 scripts/kconfig/streamline_config.pl | 2 ++
 1 file changed, 2 insertions(+)
scripts/kconfig/streamline_config.pl +2 -0
index 059061b6daef..044829972ba5 100755
@@ -702,3 +702,5 @@ foreach my $module (keys(%modules)) {
 	print STDERR "\n";
     }
 }
+
+# vim: softtabstop=4
Signature · 1 line
2.30.1
#3 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 9 lines · Steven Rostedt

From: "Steven Rostedt (VMware)" <[email protected]>

The tab stop for Perl files is by default (at least in emacs) to be 4 spaces, where a tab is used for all 8 spaces. Add a local variable comment to make vim do the same by default, and this will help keep the file consistent in the future when others edit it via vim and not emacs.

Documentation/process/coding-style.rst says "do not do this".

Rather, I want to remove this ugly stuff entirely.
https://lore.kernel.org/patchwork/patch/1401439/

Adding .editorconfig seems OK to me, but Doing this in individual files in an editor-specific manner is a horror.

Quoted 18 lines
---
 scripts/kconfig/streamline_config.pl | 2 ++
 1 file changed, 2 insertions(+)
scripts/kconfig/streamline_config.pl +2 -1
index 059061b6daef..044829972ba5 100755
@@ -702,3 +702,5 @@ foreach my $module (keys(%modules)) {
        print STDERR "\n";
     }
 }
+
+# vim: softtabstop=4
--

2.30.1

Signature · 2 lines
Best Regards
Masahiro Yamada
#4 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 9 lines · On Wed, 24 Mar 2021 15:01:13 +0900 Masahiro Yamada <[email protected]> wrote:
Quoted 8 lines · Steven Rostedt

From: "Steven Rostedt (VMware)" <[email protected]>

The tab stop for Perl files is by default (at least in emacs) to be 4 spaces, where a tab is used for all 8 spaces. Add a local variable comment to make vim do the same by default, and this will help keep the file consistent in the future when others edit it via vim and not emacs.

Quoted 4 lines
Quoted 1 line

Documentation/process/coding-style.rst says "do not do this".

I take that file more as for C code, never took it for Perl ;-)

Quoted 3 lines

Rather, I want to remove this ugly stuff entirely.
https://lore.kernel.org/patchwork/patch/1401439/

And I totally agree it does not belong in C code.

Quoted 4 lines

Adding .editorconfig seems OK to me, but Doing this in individual files in an editor-specific manner is a horror.

Is there a way to add this for the directory?

The reason I added this was because of the different ways that vim and emacs handle Perl files. I just added this to ktest.pl because I want it to be consistent.

The emacs way to edit Perl is to have 4 space indentation, but use tabs for every 8 spaces. That is, you have:

    (4 spaces)
	(1 tab)
	    (1 tab and 4 spaces)
		(2 tabs)
		    (2 tabs and 4 spaces)

etc.

What I found from people who edit Perl code is that they will either just indent 8 (with tabs), or just use all spaces. Then you have:

(1 tab and 4 spaces)
(followed by 12 spaces!)

The way to make vim work the same is to add the softtabspace=4 command.

We can not add this, but then have to either police the patches coming in, or constantly clean up the code after the fact.

This code doesn't change much, so I'm fine with that. But for ktest.pl, I'm adding it.

-- Steve

#5 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 2 lines · On Wed, 24 Mar 2021 09:54:17 -0400 Steven Rostedt <[email protected]> wrote:

This code doesn't change much, so I'm fine with that. But for ktest.pl, I'm adding it.

Anyway, I'm not going to ask you to take the second patch if you don't like it, but would you take the first patch?

-- Steve

#6 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

In reply to Steven Rostedt
Quoted 40 lines · Steven Rostedt
Quoted 9 lines · On Wed, 24 Mar 2021 15:01:13 +0900 Masahiro Yamada <[email protected]> wrote:
Quoted 8 lines · Steven Rostedt

From: "Steven Rostedt (VMware)" <[email protected]>

The tab stop for Perl files is by default (at least in emacs) to be 4 spaces, where a tab is used for all 8 spaces. Add a local variable comment to make vim do the same by default, and this will help keep the file consistent in the future when others edit it via vim and not emacs.

Quoted 4 lines
Quoted 1 line

Documentation/process/coding-style.rst says "do not do this".

I take that file more as for C code, never took it for Perl ;-)

Quoted 3 lines

Rather, I want to remove this ugly stuff entirely.
https://lore.kernel.org/patchwork/patch/1401439/

And I totally agree it does not belong in C code.

Quoted 4 lines

Adding .editorconfig seems OK to me, but Doing this in individual files in an editor-specific manner is a horror.

Is there a way to add this for the directory?

The reason I added this was because of the different ways that vim and emacs handle Perl files. I just added this to ktest.pl because I want it to be consistent.

The emacs way to edit Perl is to have 4 space indentation, but use tabs for every 8 spaces. That is, you have:

Quoted 7 lines
    (4 spaces)
        (1 tab)
            (1 tab and 4 spaces)
                (2 tabs)
                    (2 tabs and 4 spaces)

etc.

The root cause of inconsistency is that
you mix up space-indentation and tab-indentation. I do not know if it is a standard way either.

For example, scripts/checkpatch.pl uses only tabs, which I think is more robust.

Unfortunately, we do not have standardized indentation style for scripts yet, and people can go in any direction.

The editorconfig patch [1] proposed to always use 4-space indentation for *.pl files.
(that is, do not replace 8 spaces with a tab).

I do not know whether the kernel will adopt .editorconfig or not, but if that patch is applied, your 1/2 will be a step backward.

My got-feeling is, you will never reach the goal as long as you adopt a strange indentation style, which is obscure to other contributors.

Not all people use vim.
I am not interested in 1/2 either.

If you insist on this patch set, apply it to your tree and send a pull request by yourself.

[1]: https://lore.kernel.org/lkml/[email protected]/

Quoted 16 lines

What I found from people who edit Perl code is that they will either just indent 8 (with tabs), or just use all spaces. Then you have:

(1 tab and 4 spaces)
(followed by 12 spaces!)

The way to make vim work the same is to add the softtabspace=4 command.

We can not add this, but then have to either police the patches coming in, or constantly clean up the code after the fact.

This code doesn't change much, so I'm fine with that. But for ktest.pl, I'm adding it.

-- Steve

Signature · 2 lines
Best Regards
Masahiro Yamada
#7 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 4 lines · On Thu, 25 Mar 2021 15:20:13 +0900 Masahiro Yamada <[email protected]> wrote:

The root cause of inconsistency is that
you mix up space-indentation and tab-indentation.
I do not know if it is a standard way either.

This is the default way emacs has edited perl files for as long as I can remember (back to 1996). It became my standard of editing perl files just because of that. For everything else, I use tabs.

Quoted 3 lines

For example, scripts/checkpatch.pl uses only tabs, which I think is more robust.

Probably because Joe probably uses vim ;-)

Quoted 7 lines

Unfortunately, we do not have standardized indentation style for scripts yet, and people can go in any direction.

The editorconfig patch [1] proposed to always use 4-space indentation for *.pl files.
(that is, do not replace 8 spaces with a tab).

I rather have all tabs, or the tab and spaces. I find 8 spaces to be a waste of memory and disk space.

Quoted 3 lines

I do not know whether the kernel will adopt .editorconfig or not, but if that patch is applied, your 1/2 will be a step backward.

My 1/2 only made it consistent, as the original code had the tab/spaces mix and just a few lines that were modified by others broke it by adding all spaces.

Quoted 4 lines

My got-feeling is, you will never reach the goal as long as you adopt a strange indentation style, which is obscure to other contributors.

I'm guessing this is not strange to other perl developers who uses emacs.

Quoted 2 lines

Not all people use vim.

I don't use it either. I was trying to make vim match emacs. Of course for those that use something else, it wont help. I'm curious, what's your main editor that you use?

Quoted 1 line

I am not interested in 1/2 either.

OK.

Quoted 3 lines

If you insist on this patch set, apply it to your tree and send a pull request by yourself.

I'm fine with that.

Quoted 3 lines

[1]: https://lore.kernel.org/lkml/[email protected]/

Thanks for the link.

-- Steve

#8 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 43 lines · Steven Rostedt
Quoted 4 lines · On Thu, 25 Mar 2021 15:20:13 +0900 Masahiro Yamada <[email protected]> wrote:

The root cause of inconsistency is that
you mix up space-indentation and tab-indentation.
I do not know if it is a standard way either.

This is the default way emacs has edited perl files for as long as I can remember (back to 1996). It became my standard of editing perl files just because of that. For everything else, I use tabs.

Quoted 3 lines

For example, scripts/checkpatch.pl uses only tabs, which I think is more robust.

Probably because Joe probably uses vim ;-)

Quoted 7 lines

Unfortunately, we do not have standardized indentation style for scripts yet, and people can go in any direction.

The editorconfig patch [1] proposed to always use 4-space indentation for *.pl files.
(that is, do not replace 8 spaces with a tab).

I rather have all tabs, or the tab and spaces. I find 8 spaces to be a waste of memory and disk space.

Quoted 3 lines

I do not know whether the kernel will adopt .editorconfig or not, but if that patch is applied, your 1/2 will be a step backward.

My 1/2 only made it consistent, as the original code had the tab/spaces mix and just a few lines that were modified by others broke it by adding all spaces.

Quoted 4 lines

My got-feeling is, you will never reach the goal as long as you adopt a strange indentation style, which is obscure to other contributors.

Quoted 8 lines

I'm guessing this is not strange to other perl developers who uses emacs.

Quoted 2 lines

Not all people use vim.

I don't use it either. I was trying to make vim match emacs. Of course for those that use something else, it wont help. I'm curious, what's your main editor that you use?

I use emacs.

I have some setups in my ~/.emacs although I am not an expert of emacs lisp.

(defalias 'perl-mode 'cperl-mode)

(add-hook 'cperl-mode-hook
(lambda()
(setq cperl-indent-level 8)
(setq cperl-tab-always-indent t)
(setq tab-width 8)
(setq indent-tabs-mode t) ))

Then, emacs can understand that my preference is tab-indentation with 8 character width.

Quoted 18 lines
Quoted 2 lines

I am not interested in 1/2 either.

OK.

Quoted 3 lines

If you insist on this patch set, apply it to your tree and send a pull request by yourself.

I'm fine with that.

Quoted 3 lines

[1]: https://lore.kernel.org/lkml/[email protected]/

Thanks for the link.

-- Steve

Signature · 2 lines
Best Regards
Masahiro Yamada
#9 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

Quoted 26 lines · On Thu, 25 Mar 2021 23:09:38 +0900 Masahiro Yamada <[email protected]> wrote:
Quoted 5 lines
Quoted 1 line

Not all people use vim.

I don't use it either. I was trying to make vim match emacs. Of course for those that use something else, it wont help. I'm curious, what's your main editor that you use?

I use emacs.

I have some setups in my ~/.emacs although I am not an expert of emacs lisp.

(defalias 'perl-mode 'cperl-mode)

(add-hook 'cperl-mode-hook
(lambda()
(setq cperl-indent-level 8)
(setq cperl-tab-always-indent t)
(setq tab-width 8)
(setq indent-tabs-mode t) ))

Quoted 3 lines

Then, emacs can understand that my preference is tab-indentation with 8 character width.

Ah, so you edited your perl-mode to not use the emacs default. I never did.

I was just letting you know where I picked up the "mix up space-indentation and tab-indentation" from ;-) I'm sure if you removed those lines, you would then see why I use that "standard".

I've been doing it for so long on all my perl files, it's been engraved in me to do it that way whenever I work on perl.

-- Steve

#10 lore raw

Re: [PATCH 2/2] streamline_config.pl: Add softtabstop=4 for vim users

In reply to Steven Rostedt
Quoted 9 lines · Steven Rostedt
Quoted 4 lines · On Thu, 25 Mar 2021 15:20:13 +0900 Masahiro Yamada <[email protected]> wrote:

The root cause of inconsistency is that you mix up space-indentation and tab-indentation. I do not know if it is a standard way either.

This is the default way emacs has edited perl files for as long as I can remember (back to 1996). It became my standard of editing perl files just because of that. For everything else, I use tabs.

[]

Quoted 4 lines
Quoted 2 lines

For example, scripts/checkpatch.pl uses only tabs, which I think is more robust.

Probably because Joe probably uses vim ;-)

I generally use emacs. Maybe Andy Whitcroft uses vim.
For checkpatch.pl I just followed Andy's style. get_maintainer.pl uses the 4 spaces then 1 tab style like Steven uses.

perl code can be pretty long left to right so using smaller indentation seems useful there.