From: Tony Lindgren <tony@atomide.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"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-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"kernel test robot" <oliver.sang@intel.com>
Subject: Re: [PATCH v2 1/1] serial: core: Fix serial_base_match() after fixing controller port name
Date: Sun, 6 Aug 2023 09:23:30 +0300 [thread overview]
Message-ID: <20230806062330.GM14799@atomide.com> (raw)
In-Reply-To: <20230806043357.GL14799@atomide.com>
* Tony Lindgren <tony@atomide.com> [230806 07:34]:
> To me it seems we can't use port->port_id until multiport drivers
> initialize it, or set port->port_id automatically with ida_alloc().
>
> Meanwhile, we can just change back to using port->line assuming that
> fixes the issue for your tests. This means the port names are broken
> like we had in -rc1 but that's a cosmetic issue for now.
Sent it with a proper patch description [0].
Regards,
Tony
[0] https://lore.kernel.org/linux-serial/20230806062052.47737-1-tony@atomide.com/T/#u
prev parent reply other threads:[~2023-08-06 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 7:10 [PATCH v2 1/1] serial: core: Fix serial_base_match() after fixing controller port name Tony Lindgren
2023-08-03 7:26 ` Jiri Slaby
2023-08-03 7:50 ` Greg Kroah-Hartman
2023-08-03 8:52 ` Conor Dooley
2023-08-03 15:34 ` Biju Das
2023-08-04 21:42 ` Guenter Roeck
2023-08-05 4:49 ` Tony Lindgren
2023-08-05 10:50 ` Guenter Roeck
2023-08-05 11:48 ` Tony Lindgren
2023-08-05 15:50 ` Guenter Roeck
2023-08-05 16:12 ` Guenter Roeck
2023-08-06 4:33 ` Tony Lindgren
2023-08-06 6:23 ` Tony Lindgren [this message]
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=20230806062330.GM14799@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@intel.com \
--cc=andriy.shevchenko@linux.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-serial@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oliver.sang@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox