lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 03 Mar 2020 15:35:46 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     rmk+kernel@...linux.org.uk
Cc:     kuba@...nel.org, corbet@....net, netdev@...r.kernel.org,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next] doc: sfp-phylink: correct code indentation

From: Russell King <rmk+kernel@...linux.org.uk>
Date: Tue, 03 Mar 2020 13:29:42 +0000

> Using vim to edit the phylink documentation reveals some mistakes due
> to the "invisible" pythonesque white space indentation that can't be
> seen with other editors. Fix it.
> 
> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>

I applied this, but you do know that GIT is going to warn about the
trailing whitespace to me:

.git/rebase-apply/patch:29: trailing whitespace.
	
.git/rebase-apply/patch:39: trailing whitespace.
	
warning: 2 lines add whitespace errors.

Do the empty lines really need that leading TAB?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ