All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 0/2] tty: serial: imx: fix lockup and garbage on SMP
Date: Tue, 28 Aug 2012 08:03:18 +0200	[thread overview]
Message-ID: <503C5F26.4020108@de.bosch.com> (raw)
In-Reply-To: <20120827233756.GH2281@r65073-Latitude-D630>

On 28.08.2012 01:37, Shawn Guo wrote:
> On Mon, Aug 27, 2012 at 03:51:42PM -0700, Greg Kroah-Hartman wrote:
>> On both of them?  I can do that if needed.  How far back should they go?
>>
> It should be okay to apply on 3.4 and 3.5. 

For patch #1/2: Yes, thanks!

> But patch #2 is still in
> question.  I do not like the #ifdef.

For patch #2/2: Yes, understood. I'll look at Troy's proposal and will 
update #2/2.

Many thanks and best regards

Dirk

WARNING: multiple messages have this Message-ID (diff)
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] tty: serial: imx: fix lockup and garbage on SMP
Date: Tue, 28 Aug 2012 08:03:18 +0200	[thread overview]
Message-ID: <503C5F26.4020108@de.bosch.com> (raw)
In-Reply-To: <20120827233756.GH2281@r65073-Latitude-D630>

On 28.08.2012 01:37, Shawn Guo wrote:
> On Mon, Aug 27, 2012 at 03:51:42PM -0700, Greg Kroah-Hartman wrote:
>> On both of them?  I can do that if needed.  How far back should they go?
>>
> It should be okay to apply on 3.4 and 3.5. 

For patch #1/2: Yes, thanks!

> But patch #2 is still in
> question.  I do not like the #ifdef.

For patch #2/2: Yes, understood. I'll look at Troy's proposal and will 
update #2/2.

Many thanks and best regards

Dirk

  reply	other threads:[~2012-08-28  6:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27  7:36 [PATCH 0/2] tty: serial: imx: fix lockup and garbage on SMP Dirk Behme
2012-08-27  7:36 ` Dirk Behme
2012-08-27  7:36 ` [PATCH 1/2] tty: serial: imx: console write routing is unsafe " Dirk Behme
2012-08-27  7:36   ` Dirk Behme
2012-08-27 22:33   ` Shawn Guo
2012-08-27 22:33     ` Shawn Guo
2012-08-27  7:36 ` [PATCH 2/2] tty: serial: imx: don't reinit clock with enabled console Dirk Behme
2012-08-27  7:36   ` Dirk Behme
2012-08-27 18:20   ` Troy Kisky
2012-08-27 18:20     ` Troy Kisky
2012-08-28 10:46     ` Dirk Behme
2012-08-28 10:46       ` Dirk Behme
2012-08-28 18:27       ` Troy Kisky
2012-08-28 18:27         ` Troy Kisky
2012-08-28 18:45         ` Troy Kisky
2012-08-28 18:45           ` Troy Kisky
2012-08-27 22:31 ` [PATCH 0/2] tty: serial: imx: fix lockup and garbage on SMP Shawn Guo
2012-08-27 22:31   ` Shawn Guo
2012-08-27 22:51   ` Greg Kroah-Hartman
2012-08-27 22:51     ` Greg Kroah-Hartman
2012-08-27 23:37     ` Shawn Guo
2012-08-27 23:37       ` Shawn Guo
2012-08-28  6:03       ` Dirk Behme [this message]
2012-08-28  6:03         ` Dirk Behme

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=503C5F26.4020108@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    /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.