linux-kernel - [PATCH] LIRC: Add missing line breaks

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

Date:	Fri, 26 Sep 2008 21:27:16 +0200
From:	Stefan Bauer <stefan.bauer@...tu-chemnitz.de>
To:	Jarod Wilson <jwilson@...hat.com>
Cc:	Janne Grunau <j@...nau.net>, linux-kernel@...r.kernel.org
Subject: [PATCH] LIRC: Add missing line breaks

From: Stefan Bauer <stefan.bauer@...tu-chemnitz.de>

Add missing line breaks to lirc_buffer_{clear, free}() warnings.

Signed-Off-By: Stefan Bauer <stefan.bauer@...tu-chemnitz.de>

---
Jarod, this is for your linux-2.6-lirc.git tree and fixes output like this:
calling lirc_buffer_clear on an uninitialized lirc_bufferModules linked in

diff --git a/drivers/input/lirc/lirc_dev.h b/drivers/input/lirc/lirc_dev.h
index 1342035..bf05a7c 100644
--- a/drivers/input/lirc/lirc_dev.h
+++ b/drivers/input/lirc/lirc_dev.h
@@ -34,7 +34,7 @@ static void lirc_buffer_clear(struct lirc_buffer *buf)
 	if (buf->fifo)
 		kfifo_reset(buf->fifo);
 	else
-		WARN(1, "calling lirc_buffer_clear on an uninitialized lirc_buffer");
+		WARN(1, "calling lirc_buffer_clear on an uninitialized lirc_buffer\n");
 }
 static int lirc_buffer_init(struct lirc_buffer *buf,
 				    unsigned int chunk_size,
@@ -54,7 +54,7 @@ static void lirc_buffer_free(struct lirc_buffer *buf)
 	if (buf->fifo)
 		kfifo_free(buf->fifo);
 	else
-		WARN(1, "calling lirc_buffer_free on an uninitialized lirc_buffer");
+		WARN(1, "calling lirc_buffer_free on an uninitialized lirc_buffer\n");
 }
 static int lirc_buffer_full(struct lirc_buffer *buf)
 {

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