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]
Message-ID: <53C92535.2010605@nod.at>
Date:	Fri, 18 Jul 2014 15:46:29 +0200
From:	Richard Weinberger <richard@....at>
To:	Guenter Roeck <linux@...ck-us.net>, Borislav Petkov <bp@...e.de>
CC:	akpm@...ux-foundation.org, apw@...onical.com, joe@...ches.com,
	tytso@....edu, dwalter@...gle.com, neilb@...e.de,
	hch@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] checkpatch.pl: Remove --file option

Am 18.07.2014 15:37, schrieb Guenter Roeck:
> On 07/18/2014 01:23 AM, Borislav Petkov wrote:
>> On Fri, Jul 18, 2014 at 12:29:37AM -0700, Guenter Roeck wrote:
>>> First, 'abuse' is a relative term. It describes a use you
>>> (and possibly many others) may find objectionable, but that
>>> does not mean all uses are objectionable.
>>
>> Do you actually have a valid use case for keeping the cmdline switch ...
>>
> 
> I find it convenient to be able to check a new file before committing it
> and creating a patch. Also, I find it convenient to be able use it to clean
> up a file before I do heavy lifting with it. Yes, I understand the latter
> is discouraged nowadays, and I would not use it anymore outside my scope
> of responsibility unless specifically asked by the maintainer to do so,
> but in such cases it helps me a lot to be able to address the cleanup
> prior to the heavy lifting.

As capable kernel hacker you can still use a command like:
diff -urN /dev/null $file | ./scripts/checkpatch.pl -

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ