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:	Fri, 5 Dec 2014 15:28:55 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Luis de Bethencourt <luis@...ethencourt.com>
Cc:	m.chehab@...sung.com, devel@...verdev.osuosl.org,
	gulsah.1004@...il.com, gregkh@...uxfoundation.org,
	jarod@...sonet.com, linux-kernel@...r.kernel.org,
	tuomas.tynkkynen@....fi, linux-media@...r.kernel.org
Subject: Re: [PATCH v3 2/2] staging: media: lirc: lirc_zilog.c: keep
 consistency in dev functions

On Thu, Dec 04, 2014 at 10:35:24PM +0000, Luis de Bethencourt wrote:
> The previous patch switched some dev functions to move the string to a second
> line. Doing this for all similar functions because it makes the driver easier
> to read if all similar lines use the same criteria.
> 
> Signed-off-by: Luis de Bethencourt <luis@...ethencourt.com>
> ---
>  drivers/staging/media/lirc/lirc_zilog.c | 155 +++++++++++++++++++++-----------
>  1 file changed, 102 insertions(+), 53 deletions(-)
> 
> diff --git a/drivers/staging/media/lirc/lirc_zilog.c b/drivers/staging/media/lirc/lirc_zilog.c
> index 8814a7e..af46827 100644
> --- a/drivers/staging/media/lirc/lirc_zilog.c
> +++ b/drivers/staging/media/lirc/lirc_zilog.c
> @@ -322,7 +322,8 @@ static int add_to_buf(struct IR *ir)
>  	struct IR_tx *tx;
>  
>  	if (lirc_buffer_full(rbuf)) {
> -		dev_dbg(ir->l.dev, "buffer overflow\n");
> +		dev_dbg(ir->l.dev,
> +			"buffer overflow\n");

No.  Don't do this.  It's better if it is on one line.

regards,
dan carpenter

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ