linux-kernel - Re: [PATCH 3/3] Staging: rts5208: Coding style warnings fix for 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 29 Sep 2015 02:25:50 +0200
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Punit Vara <punitvara@...il.com>
Cc:	joe@...ches.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Staging: rts5208: Coding style warnings fix for
 block comments

On Mon, Sep 21, 2015 at 11:29:50PM +0530, Punit Vara wrote:
> This patch is to rtsx_chip.h that fixes up following warning reported
> by checkpatch.pl :
> 
> -Block comments use * on subsequent lines
> -Block comments use a trailing */ on a separate line
> 
> Signed-off-by: Punit Vara <punitvara@...il.com>
> ---
>  drivers/staging/rts5208/rtsx_chip.h | 66 +++++++++++++++++++++++--------------
>  1 file changed, 42 insertions(+), 24 deletions(-)

Where is patch 1/3 and 2/3?

You have sent me almost 60 different patches, yet you gave me no idea
what order to apply them in at all, what am I supposed to do with all of
them?

Please redo all of your outstanding patches that I have not taken and
resend them in a proper patch series, numbered correctly so that I have
a chance to know what order to apply the.  I've now purged my todo queue
of all of your patches.

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/