linux-kernel - Re: [PATCH] staging: android: logger: Allocate logs dynamically at boot

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: <20120507195628.GA9977@kroah.com>
Date:	Mon, 7 May 2012 12:56:28 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Tim Bird <tim.bird@...sony.com>
Cc:	Brian Swetland <swetland@...gle.com>,
	linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: android: logger: Allocate logs dynamically at
 boot

On Mon, May 07, 2012 at 12:14:04PM -0700, Tim Bird wrote:
> BTW, I have a whitespace cleanup for one of my previous patches.  I'm unsure
> if I should send this in, or wait until the code in question is affected
> by another patch.  I thought the standard kernel policy was to not do
> standalone whitespace cleanup patches (especially trivial ones).  But
> is that the same policy for staging?

No, the policy is to do stand-alone whitespace cleanup patches,
especially trivial ones :)

Well, for portions of the kernel I maintain at least, I don't mind them
at all, send them on when you have them.

thanks,

greg k-h
--
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/