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: <1389114734.3095.3.camel@buesod1.americas.hpqcorp.net>
Date:	Tue, 07 Jan 2014 09:12:14 -0800
From:	Davidlohr Bueso <davidlohr@...com>
To:	Manfred Spraul <manfred@...orfullife.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Davidlohr Bueso <davidlohr.bueso@...com>,
	Rik van Riel <riel@...hat.com>, Joe Perches <joe@...ches.com>
Subject: Re: [PATCH] ipc: whitespace cleanup

On Tue, 2013-12-24 at 16:02 +0100, Manfred Spraul wrote:
> The ipc code does not adhere the typical linux coding style.
> This patch fixes lots of simple whitespace errors.

While it's no big deal, the title of the patch doesn't really reflect
the actual changes as it deals with much more than just whitespace
cleanups. How about something like "ipc: checkpatch fixes"?

> 
> - mostly autogenerated by
>   scripts/checkpatch.pl -f --fix \
> 	--types=pointer_location,spacing,space_before_tab
> - one manual fixup (keep structure members tab-aligned)
> - removal of additional space_before_tab that were not found by --fix
> 
> diff -w is empty.
> Tested with some of my msg and sem test apps.
> 
> Andrew: Could you include it in -mm and move it towards Linus' tree?

This patch doesn't apply on top of linux-next (which now includes
Rafael's changes), could you please resend? I'm planning some more
cleanups on top of this so, if Andrew agrees, I can include these
changes to my patchset.

Thanks,
Davidlohr

--
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