linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Michal Simek <michal.simek@xilinx.com>,
	linux-kernel@vger.kernel.org, monstr@monstr.eu
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>,
	Peter Hurley <peter@hurleysoftware.com>,
	Alan Cox <alan@linux.intel.com>, Tony Lindgren <tony@atomide.com>,
	Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 2/2] tty: serial: 8250_core: Check that port->line is >=0
Date: Fri, 16 Jan 2015 11:51:12 +0100	[thread overview]
Message-ID: <54B8ED20.60308@linutronix.de> (raw)
In-Reply-To: <df5d7450de9f4382b1cb43791f69e25c@BL2FFO11FD013.protection.gbl>

- Yoshihiro YUNOMAE
(reason: 550 5.1.1 <yoshihiro.yunomae.ez@hitachi.com>: Recipient
address rejected: User Unknown)

On 01/16/2015 11:37 AM, Michal Simek wrote:
> Hi,

Hi,

> Origin patch looks good to me but this checking will be good to add.
> Are you using of_serial.c because I didn't find any of_alias_get_id call
> for 8250?

I'm using of_alias_get_id() in 8250_omap.c which made it into
v3.19-rc1. I think the change you mention made it one release earlier.

> Your logic here is a little bit different than I have in my tree.
> (Some sort of pl011 solution). You don't need to failed if you port.line is
> below 0 but if you are not able to read aliases port enumeration
> may be unpredictable.

For omap we should have valid aliases because we have multiple UARTs.
So the platform id should always be >=0 and the DT includes it already.
And Tony wanted to have predicted numbers so I don't mind to fail here.
Also it is nice if you have ttyS2 which maps UART2 in the manual even
without having ttyS[01].

> Thanks,
> Michal

Sebastian


  reply	other threads:[~2015-01-16 10:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 14:55 [PATCH 1/2] tty: serial: 8250_core: Remove trailing whitespaces Michal Simek
2015-01-15 14:55 ` [PATCH 2/2] tty: serial: 8250_core: Check that port->line is >=0 Michal Simek
2015-01-16  9:00   ` Sebastian Andrzej Siewior
2015-01-16 10:37     ` Michal Simek
2015-01-16 10:51       ` Sebastian Andrzej Siewior [this message]
2015-01-16 11:02         ` Michal Simek
2015-01-16 11:33           ` Sebastian Andrzej Siewior
2015-01-30 23:23   ` Greg Kroah-Hartman
2015-02-02  8:09     ` Michal Simek
2015-02-02 10:49       ` Andy Shevchenko
2015-01-30 23:22 ` [PATCH 1/2] tty: serial: 8250_core: Remove trailing whitespaces Greg Kroah-Hartman
2015-02-02  8:08   ` Michal Simek
2015-02-02 18:43     ` Greg Kroah-Hartman

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=54B8ED20.60308@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=alan@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=mingo@elte.hu \
    --cc=monstr@monstr.eu \
    --cc=peter@hurleysoftware.com \
    --cc=ricardo.ribalda@gmail.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).