linux-kernel - Re: [PATCH 1/2] Staging: comedi: Coding style issues

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

Date:	Tue, 23 Aug 2011 11:56:10 -0700
From:	Greg KH <greg@...ah.com>
To:	markpearson_de@...oo.de
Cc:	abbotti@....co.uk, fmhess@...rs.sourceforge.net,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Staging: comedi: Coding style issues

On Sun, Jul 10, 2011 at 09:16:37PM +0200, markpearson_de@...oo.de wrote:
> From: Mark Pearson <markpearson_de@...oo.de>
> 
> comedi.h : static inline decleration placed on the same line as the end
>            bracket from the previous static inline decleration.
>            Bracket coding issue also cleaned-up.
> 
> Signed-off-by: Mark Pearson <markpearson_de@...oo.de>
> ---
>  drivers/staging/comedi/comedi.h |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/staging/comedi/comedi.h b/drivers/staging/comedi/comedi.h
> index 6c900e2..ed6854c 100644
> --- a/drivers/staging/comedi/comedi.h
> +++ b/drivers/staging/comedi/comedi.h
> @@ -514,7 +514,9 @@
>  			return 0x1 + pfi_channel;
>  		else
>  			return 0xb + pfi_channel;
> -	} static inline unsigned NI_USUAL_RTSI_SELECT(unsigned rtsi_channel) {
> +	}
> +	static inline unsigned NI_USUAL_RTSI_SELECT(unsigned rtsi_channel)
> +	{

This patch does not apply anymore to 3.1-rc3, care to resend?

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/