[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfHtTV6L0GE61kMiHMCQrUSwGJPRxsiNuOCD9mY7MPpZQ@mail.gmail.com>
Date: Wed, 22 Mar 2017 20:45:51 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Vignesh R <vigneshr@...com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Jisheng Zhang <jszhang@...vell.com>
Subject: Re: [PATCH 1/2] tty: serial_core: Add name field to uart_port struct
On Tue, Mar 21, 2017 at 3:36 PM, Vignesh R <vigneshr@...com> wrote:
> Introduce a field to store name of uart_port that can be used to easily
> identify uart port instances on a system that has more than one uart
uart -> UART
> instance. The name is of the form ttyXN(eg. ttyS0, ttyAMA0,..) where N
> is number that particular uart instance.
> This field will be useful when printing debug info for a particular port
> or in register irqs with unique irq name. Port name is populated during
irq(s) -> IRQ(s)
> uart_add_one_port().
> + snprintf(uport->name, sizeof(uport->name), "%s%d", drv->dev_name,
> + drv->tty_driver->name_base + uport->line);
This is fragile. dev_name is defined as pointer, so, it would be any length.
So, better to use [devm_]kasprintf().
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists