From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: don't announce CIR serial ports
Date: Mon, 3 Aug 2015 16:40:12 -0700 [thread overview]
Message-ID: <20150803234012.GA31555@kroah.com> (raw)
In-Reply-To: <55BE8725.6090303@maciej.szmigiero.name>
On Sun, Aug 02, 2015 at 11:09:57PM +0200, Maciej S. Szmigiero wrote:
> CIR type serial ports aren't real serial ports.
> This is just a way to prevent legacy serial driver
> from probing and eventually binding some resources
> so don't announce them like normal serial ports.
>
> Signed-off-by: Maciej Szmigiero <mail@maciej.szmigiero.name>
> ---
> drivers/tty/serial/serial_core.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index f368520..99f944d 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -2237,7 +2237,7 @@ uart_configure_port(struct uart_driver *drv, struct uart_state *state,
> port->ops->config_port(port, flags);
> }
>
> - if (port->type != PORT_UNKNOWN) {
> + if (port->type != PORT_UNKNOWN && port->type != PORT_8250_CIR) {
> unsigned long flags;
>
> uart_report_port(drv, port);
This does not seem correct, why is this type of "port" somehow special
that it should be skiped?
thanks,
greg k-h
next prev parent reply other threads:[~2015-08-03 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 21:09 [PATCH] serial: don't announce CIR serial ports Maciej S. Szmigiero
2015-08-03 23:40 ` Greg Kroah-Hartman [this message]
2015-08-04 0:40 ` Maciej S. Szmigiero
2015-08-04 1:46 ` Peter Hurley
2015-08-04 23:25 ` Maciej S. Szmigiero
2015-08-05 2:03 ` Peter Hurley
2015-08-05 12:35 ` Maciej S. Szmigiero
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=20150803234012.GA31555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
/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