From: Tony Lindgren <tony@atomide.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Dhruva Gole" <d-gole@ti.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"John Ogness" <john.ogness@linutronix.de>,
"Johan Hovold" <johan@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: core: Add support for dev_name:0.0 naming for kernel console
Date: Wed, 19 Jul 2023 08:28:11 +0300 [thread overview]
Message-ID: <20230719052811.GH5194@atomide.com> (raw)
In-Reply-To: <35758c24-1543-6f96-7957-b371dc94e59d@kernel.org>
* Jiri Slaby <jirislaby@kernel.org> [230719 05:25]:
> On 19. 07. 23, 7:15, Tony Lindgren wrote:
> > +/*
> > + * Add preferred console if configured on kernel command line with naming
> > + * "console=dev_name:0.0".
> > + */
> > +static int serial_core_add_preferred_console(struct uart_driver *drv,
> > + struct uart_port *port)
> > +{
> > + char *port_match, *opt, *name;
> > + int len, ret = 0;
> > +
> > + port_match = kasprintf(GFP_KERNEL, "console=%s:%i.%i",
> > + dev_name(port->dev), port->ctrl_id,
> > + port->port_id);
> > + if (!port_match)
> > + return -ENOMEM;
> > +
> > + opt = strstr(saved_command_line, port_match);
> > + if (!opt)
> > + goto free_port_match;
> > +
> > + len = strlen(port_match);
> > +
> > + if (strlen(opt) > len + 1 && opt[len] == ',')
> > + opt += len + 1;
> > + else
> > + opt = NULL;
> > +
> > + name = kstrdup(drv->dev_name, GFP_KERNEL);
>
> Why do you dup the name here?
I was getting ignoring const warning, but maybe the right solution is
to just use const char *name here.. Let me check.
Regards,
Tony
next prev parent reply other threads:[~2023-07-19 5:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 5:15 [PATCH] serial: core: Add support for dev_name:0.0 naming for kernel console Tony Lindgren
2023-07-19 5:25 ` Jiri Slaby
2023-07-19 5:28 ` Tony Lindgren [this message]
2023-07-19 5:29 ` Jiri Slaby
2023-07-19 5:32 ` Tony Lindgren
2023-07-19 5:36 ` Jiri Slaby
2023-07-19 5:49 ` Tony Lindgren
2023-07-19 5:37 ` Andy Shevchenko
2023-07-20 4:13 ` Tony Lindgren
2023-07-19 15:38 ` kernel test robot
2023-07-19 18:03 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230719052811.GH5194@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@intel.com \
--cc=bigeasy@linutronix.de \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.