[media] lirc_zilog: Fix somewhat confusing information messages in ir_probe()

The total sequence of messages emitted by the ir_porbe() calls
for a transceiver's two i2c_clients was confusing.  Clean it up a bit.

Signed-off-by: Andy Walls <awalls@md.metrocast.net>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/drivers/staging/lirc/lirc_zilog.c b/drivers/staging/lirc/lirc_zilog.c
index 5946a9541c43..407d4b409a8b 100644
--- a/drivers/staging/lirc/lirc_zilog.c
+++ b/drivers/staging/lirc/lirc_zilog.c
@@ -1595,6 +1595,8 @@ static int ir_probe(struct i2c_client *client, const struct i2c_device_id *id)
                 ret = -EBADRQC;
                 goto out_put_xx;
         }
+        zilog_info("IR unit on %s (i2c-%d) registered as lirc%d and ready\n",
+                   adap->name, adap->nr, ir->l.minor);
 
 out_ok:
         if (rx != NULL)
@@ -1602,7 +1604,7 @@ out_ok:
         if (tx != NULL)
                 put_ir_tx(tx, true);
         put_ir_device(ir, true);
-        zilog_info("probe of IR %s on %s (i2c-%d) done. IR unit ready.\n",
+        zilog_info("probe of IR %s on %s (i2c-%d) done\n",
                    tx_probe ? "Tx" : "Rx", adap->name, adap->nr);
         mutex_unlock(&ir_devices_lock);
         return 0;