Re: [PATCH] I2C fixes for 2.6.10-rc1

From: Greg KH
Date: Fri Nov 12 2004 - 18:51:18 EST


ChangeSet 1.2095, 2004/11/12 13:20:15-08:00, khali@xxxxxxxxxxxx

[PATCH] I2C: Missing newlines in debug messages

As discussed on IRC, this simple patch fixes broken debug messages
missing their trailing newlines. I just applied something similar to
CVS, and will prepare patches for 2.4 as well.

Signed-off-by: Jean Delvare <khali@xxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <greg@xxxxxxxxx>


drivers/i2c/i2c-core.c | 2 +-
drivers/i2c/i2c-dev.c | 2 +-
drivers/i2c/i2c-sensor-detect.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)


diff -Nru a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
--- a/drivers/i2c/i2c-core.c 2004-11-12 15:22:38 -08:00
+++ b/drivers/i2c/i2c-core.c 2004-11-12 15:22:38 -08:00
@@ -760,7 +760,7 @@
if (addr == address_data->normal_i2c[i]) {
found = 1;
dev_dbg(&adapter->dev, "found normal i2c entry for adapter %d, "
- "addr %02x", adap_id,addr);
+ "addr %02x\n", adap_id, addr);
}
}

diff -Nru a/drivers/i2c/i2c-dev.c b/drivers/i2c/i2c-dev.c
--- a/drivers/i2c/i2c-dev.c 2004-11-12 15:22:38 -08:00
+++ b/drivers/i2c/i2c-dev.c 2004-11-12 15:22:38 -08:00
@@ -539,7 +539,7 @@
out_unreg_chrdev:
unregister_chrdev(I2C_MAJOR, "i2c");
out:
- printk(KERN_ERR "%s: Driver Initialisation failed", __FILE__);
+ printk(KERN_ERR "%s: Driver Initialisation failed\n", __FILE__);
return res;
}

diff -Nru a/drivers/i2c/i2c-sensor-detect.c b/drivers/i2c/i2c-sensor-detect.c
--- a/drivers/i2c/i2c-sensor-detect.c 2004-11-12 15:22:38 -08:00
+++ b/drivers/i2c/i2c-sensor-detect.c 2004-11-12 15:22:38 -08:00
@@ -115,7 +115,7 @@
for (i = 0; !found && (normal_i2c[i] != I2C_CLIENT_END); i += 1) {
if (addr == normal_i2c[i]) {
found = 1;
- dev_dbg(&adapter->dev, "found normal i2c entry for adapter %d, addr %02x", adapter_id, addr);
+ dev_dbg(&adapter->dev, "found normal i2c entry for adapter %d, addr %02x\n", adapter_id, addr);
}
}
}

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/