linux-kernel - Re: [PATCH 21/39] drivers/staging: Update WARN uses

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: <20101109235037.GB9001@kroah.com>
Date:	Tue, 9 Nov 2010 15:50:37 -0800
From:	Greg KH <greg@...ah.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Jiri Kosina <trivial@...nel.org>, devel@...verdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 21/39] drivers/staging: Update WARN uses

On Sat, Oct 30, 2010 at 02:08:38PM -0700, Joe Perches wrote:
> Add missing newlines.
> 
> Signed-off-by: Joe Perches <joe@...ches.com>
> ---
>  drivers/staging/memrar/memrar_allocator.c    |    2 +-
>  drivers/staging/solo6x10/solo6010-v4l2-enc.c |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/memrar/memrar_allocator.c b/drivers/staging/memrar/memrar_allocator.c
> index a4f8c58..705bde8 100644
> --- a/drivers/staging/memrar/memrar_allocator.c
> +++ b/drivers/staging/memrar/memrar_allocator.c
> @@ -74,7 +74,7 @@ struct memrar_allocator *memrar_create_allocator(unsigned long base,
>  	 * and issue a diagnostic.
>  	 */
>  	WARN(capacity < block_size * 2,
> -	     "memrar: Only one block available to allocator.\n");
> +	     "memrar: Only one block available to allocator\n");

There already is a new line here.  So I'll remove this part of the
patch.

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/