linux-kernel - Re: [PATCH v3] staging: lustre: lnet: klnds: Fix coding style in socklnd.c

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-next>] [day] [month] [year] [list]

Date:	Sun, 25 May 2014 16:30:39 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Masaru Nomura <massa.nomura@...il.com>
Cc:	andreas.dilger@...el.com, Oleg Drokin <green@...uxhacker.ru>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: lustre: lnet: klnds: Fix coding style in
 socklnd.c

On Sun, May 25, 2014 at 11:50:03PM +0100, Masaru Nomura wrote:
> 
> 
> 
> 2014-05-25 23:37 GMT+01:00 Greg KH <gregkh@...uxfoundation.org>:
> 
>     On Sun, May 25, 2014 at 11:24:12PM +0100, Masaru Nomura wrote:
>     > Remove prohibited space between function name and
>     > open parenthesis to meet kernel coding style.
>     > Also fix indenting due to changes to keep readability.
>     >
>     > -since v2:
>     > None. This is the resend of v2 as v2 failed to apply
> 
>     This should be below the --- line.
> 
> 
> 
> I'm sorry for that. Will fix it.
>  
> 
>     And it still doesn't apply :(
> 
>     What branch did you make it against?
> 
> 
> 
> I'm using[1] which is your staging.git (is it correct?) and downloaded it
> today.  So, there should not be a patch failure... :(

What _branch_ of that git tree did you make it against?

And please don't send html email, the mailing lists reject it.

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/