All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line
Date: Fri, 26 Jul 2013 16:05:12 -0700	[thread overview]
Message-ID: <20130726230512.GA12940@kroah.com> (raw)
In-Reply-To: <1374043721-30677-1-git-send-email-u.kleine-koenig@pengutronix.de>

On Wed, Jul 17, 2013 at 08:48:40AM +0200, Uwe Kleine-König wrote:
> pdev->id is not a valid choice for device-tree probed devices. So use
> the (properly determined) line from efm32_uart_probe consistenly.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
>  drivers/tty/serial/efm32-uart.c | 17 ++++++++++-------
>  1 file changed, 10 insertions(+), 7 deletions(-)

This patch doesn't apply, care to redo it?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-07-26 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  6:48 [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line Uwe Kleine-König
2013-07-17  6:48 ` [PATCH 2/2] serial/efm32-uart: use COMPILE_TEST symbol to extend compile test coverage Uwe Kleine-König
2013-07-26 23:05 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-30  8:21 [PATCH] serial/efm32-uart: don't slur over failure in probe_dt Uwe Kleine-König
2013-07-30  8:23 ` [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line Uwe Kleine-König
2013-07-30  8:34   ` Uwe Kleine-König
2013-07-30 14:02     ` Greg Kroah-Hartman
2013-07-30 14:37       ` Uwe Kleine-König
2013-07-30 14:51         ` 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=20130726230512.GA12940@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.