linux-kernel - Re: [PATCH] driver: staging: android: binder.c: Fixed line over 80 characters warning.

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]

Message-ID: <20140924220247.GB31890@kroah.com>
Date:	Thu, 25 Sep 2014 00:02:47 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Elshad Mustafayev <elshadimo@...il.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] driver: staging: android: binder.c: Fixed line over 80
 characters warning.

On Tue, Sep 23, 2014 at 07:12:09PM -0400, Elshad Mustafayev wrote:
> Fixed a coding style issue.
> 
> Signed-off-by: Elshad Mustafayev <elshadimo@...il.com>
> ---
>  drivers/staging/android/binder.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
> index c69c40d..71424bf 100644
> --- a/drivers/staging/android/binder.c
> +++ b/drivers/staging/android/binder.c
> @@ -664,8 +664,9 @@ static struct binder_buffer *binder_alloc_buf(struct binder_proc *proc,
>  		ALIGN(offsets_size, sizeof(void *));
>  
>  	if (size < data_size || size < offsets_size) {
> -		binder_user_error("%d: got transaction with invalid size %zd-%zd\n",
> -				proc->pid, data_size, offsets_size);
> +		binder_user_error(
> +			"%d: got transaction with invalid size %zd-%zd\n",
> +			proc->pid, data_size, offsets_size);

Nope, original code is just fine, checkpatch is giving you a
false-warning here.

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/