printk replaced with corresponding dev_err, dev_alert, dev_notice and pr_info.
pr_info has been used instead of dev_info as there is a check for port->dev 
being NULL or not.
fixed two broken user-visible strings used by the corresponding printk

Signed-off-by: Sudip Mukherjee <sudipm.mukher...@gmail.com>
---

For my previous patch ,Jiri Slaby told to investigate further as I have used 
uport->dev and there was a check for whether it is NULL. 
For this patch instead of uport->dev , i have used tty_dev as that one gave a 
better desciption of the device than uport->dev.


 drivers/tty/serial/serial_core.c | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
index 29a7be4..78aa38d 100644
--- a/drivers/tty/serial/serial_core.c
+++ b/drivers/tty/serial/serial_core.c
@@ -892,10 +892,11 @@ static int uart_set_info(struct tty_struct *tty, struct 
tty_port *port,
                         */
                        if (uport->flags & UPF_SPD_MASK) {
                                char buf[64];
-                               printk(KERN_NOTICE
-                                      "%s sets custom speed on %s. This "
-                                      "is deprecated.\n", current->comm,
-                                      tty_name(port->tty, buf));
+
+                               dev_notice(uport->dev,
+                                      "%s sets custom speed on %s. This is 
deprecated.\n",
+                                     current->comm,
+                                     tty_name(port->tty, buf));
                        }
                        uart_change_speed(tty, state, NULL);
                }
@@ -1975,12 +1976,11 @@ int uart_suspend_port(struct uart_driver *drv, struct 
uart_port *uport)
                for (tries = 3; !ops->tx_empty(uport) && tries; tries--)
                        msleep(10);
                if (!tries)
-                       printk(KERN_ERR "%s%s%s%d: Unable to drain "
-                                       "transmitter\n",
-                              uport->dev ? dev_name(uport->dev) : "",
-                              uport->dev ? ": " : "",
-                              drv->dev_name,
-                              drv->tty_driver->name_base + uport->line);
+                       dev_err(tty_dev, "%s%s%s%d: Unable to drain 
transmitter\n",
+                               uport->dev ? dev_name(uport->dev) : "",
+                               uport->dev ? ": " : "",
+                               drv->dev_name,
+                               drv->tty_driver->name_base + uport->line);
 
                if (console_suspend_enabled || !uart_console(uport))
                        ops->shutdown(uport);
@@ -2109,7 +2109,7 @@ uart_report_port(struct uart_driver *drv, struct 
uart_port *port)
                break;
        }
 
-       printk(KERN_INFO "%s%s%s%d at %s (irq = %d, base_baud = %d) is a %s\n",
+       pr_info("%s%s%s%d at %s (irq = %d, base_baud = %d) is a %s\n",
               port->dev ? dev_name(port->dev) : "",
               port->dev ? ": " : "",
               drv->dev_name,
@@ -2640,7 +2640,7 @@ int uart_add_one_port(struct uart_driver *drv, struct 
uart_port *uport)
        if (likely(!IS_ERR(tty_dev))) {
                device_set_wakeup_capable(tty_dev, 1);
        } else {
-               printk(KERN_ERR "Cannot register tty device on line %d\n",
+               dev_err(uport->dev, "Cannot register tty device on line %d\n",
                       uport->line);
        }
 
@@ -2675,7 +2675,7 @@ int uart_remove_one_port(struct uart_driver *drv, struct 
uart_port *uport)
        BUG_ON(in_interrupt());
 
        if (state->uart_port != uport)
-               printk(KERN_ALERT "Removing wrong port: %p != %p\n",
+               dev_alert(uport->dev, "Removing wrong port: %p != %p\n",
                        state->uart_port, uport);
 
        mutex_lock(&port_mutex);
-- 
1.8.1.2

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

Reply via email to