linux-kernel - Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch

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: <20160308202501.GF4153@saiyam>
Date:	Wed, 9 Mar 2016 01:55:01 +0530
From:	Saiyam Doshi <saiyamdoshi.in@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	arve@...roid.com, riandrews@...roid.com,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] staging: android: Fixed coding style issues reported
 by checkpatch

On Sun, Mar 06, 2016 at 05:21:08PM -0800, Greg KH wrote:
> You need to do only one thing per patch, please split this up into
> multiple patches.

Created two separate patches out of it having same logical change in each.

> Also verify that these are all really needed, please always work against
> linux-next, not Linus's kernel tree.

In 'drivers/staging/android/TODO' checkpatch.pl cleanup mentioned.
Also this patches are created from latest linux-next tree. How you get 
information about target kernel version for submitted patch? I mean in patch
there is no information about kernel version from which the patch is created.

View attachment "0001-staging-android-Fixed-coding-style-issue-reported-by.patch" of type "text/plain" (2736 bytes)

View attachment "0002-staging-android-Fixed-coding-style-issue-reported-by.patch" of type "text/plain" (849 bytes)