linux-kernel - Re: [PATCH v4] staging: rtl8192e: Aligning the * on each line in block comments

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 3 Feb 2017 10:51:21 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Arushi <arushisinghal19971997@...il.com>
Cc:     w.d.hubbs@...il.com, devel@...verdev.osuosl.org, kirk@...sers.ca,
        hris@...-brannons.com, speakup@...ux-speakup.org,
        linux-kernel@...r.kernel.org, samuel.thibault@...-lyon.org
Subject: Re: [PATCH v4] staging: rtl8192e: Aligning the * on each line in
 block comments

On Fri, Feb 03, 2017 at 10:56:12AM +0530, Arushi wrote:
> This patch fixes the issue by aligning the * on each line in block comments.
> [Patch v1] is rejected as the changes done is not following the linux
> coding style and [Patch v2] is rejected because forgot to mention the
> cause of rejection of [Patch v1].The cause of rejection of [Patch v3] is
> that the mention of the cause was not in the correct format.
> 
> Signed-off-by: Arushi <arushisinghal19971997@...il.com>

Note, I need a "full" name here, not just one name, unless this is what
you use to sign legal documents.

Also, you sent two different copies of this same patch, which one am I
supposed to take?

> 
> ---
> 
> In the [patch v1] to allign the * on each line in block was not correct
> as it is also not following the correct coding style of kernel so it got
> rejected and the details of all the other patch versions is given above.


This is v4, what changed in v2, v3, and v4?

Please list all of the changes, there is lots of good examples of how to
do this on the mailing list and in the documentation.

thanks,

greg k-h