linux-kernel - [PATCH] dock.c remove trailing printk whitespace

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20080523185400.GA4334@tpepper-t42p.dolavim.us>
Date:	Fri, 23 May 2008 11:54:03 -0700
From:	Tim Pepper <lnxninja@...ux.vnet.ibm.com>
To:	kristen.c.accardi@...el.com
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH] dock.c remove trailing printk whitespace

dock.c remove trailing printk whitespace

Signed-off-by: Tim Pepper <lnxninja@...ux.vnet.ibm.com>

---

I was looking at how docking events are handled these days as I was hoping
to have an event handler automatically run an xrandr script for me to
set up and remove my docking station attached monitor on dock/undock
(which I still haven't figured out how to do or if it's even supported
with my hardware :) and noticed the printk from the dock driver left
trailing whitespace in syslog.  Given the \n this doesn't look like it's
meant to be a field separator...maybe in the past?

diff --git a/drivers/acpi/dock.c b/drivers/acpi/dock.c
index fa44fb9..96c542f 100644
--- a/drivers/acpi/dock.c
+++ b/drivers/acpi/dock.c
@@ -834,7 +834,7 @@ static int dock_add(acpi_handle handle)
 		goto dock_add_err;
 	}

-	printk(KERN_INFO PREFIX "%s \n", ACPI_DOCK_DRIVER_DESCRIPTION);
+	printk(KERN_INFO PREFIX "%s\n", ACPI_DOCK_DRIVER_DESCRIPTION);

 	return 0;

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