linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Greg KH <greg@kroah.com>
Cc: Shreshtha Kumar SAHU <shreshthakumar.sahu@stericsson.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	rmk+kernel@arm.linux.org.uk, linus.walleij@stericsson.com,
	alan@linux.intel.com
Subject: Re: [PATCHv2 1/2] amba pl011: workaround for uart registers lockup
Date: Thu, 9 Jun 2011 21:46:26 +0200	[thread overview]
Message-ID: <BANLkTik18mT-AYU=myEohquwgJ12hXZzcA@mail.gmail.com> (raw)
In-Reply-To: <20110517185133.GB9105@kroah.com>

On Tue, May 17, 2011 at 8:51 PM, Greg KH <greg@kroah.com> wrote:

> Do you still want me to take this patch through the serial tree, or will
> both be going through some ARM tree?

Hm these two patches appear to be stuck in limbo, missing the
merge window and all.

Which is sad, because they fix real issues to us.

How do we proceed?

Thanks,
Linus Walleij

  reply	other threads:[~2011-06-09 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 13:01 [PATCH 1/2] amba pl011: workaround for uart registers lockup Shreshtha Kumar SAHU
2011-05-16 13:01 ` [PATCH 2/2] amba pl011: platform data for reg lockup and glitch Shreshtha Kumar SAHU
2011-05-16 13:09   ` Russell King
2011-05-16 14:00     ` Shreshtha Kumar SAHU
2011-05-16 14:05       ` Russell King
2011-05-16 14:15         ` Shreshtha Kumar SAHU
2011-05-17  5:23           ` [PATCHv2 " Shreshtha Kumar SAHU
2011-05-16 17:29 ` [PATCH 1/2] amba pl011: workaround for uart registers lockup Greg KH
2011-05-17  5:20   ` [PATCHv2 " Shreshtha Kumar SAHU
2011-05-17 18:23     ` Greg KH
2011-05-17 18:30       ` Russell King
2011-05-17 18:40         ` Greg KH
2011-05-17 18:45           ` Russell King
2011-05-17 18:51       ` Greg KH
2011-06-09 19:46         ` Linus Walleij [this message]
2011-06-09 20:11           ` Greg KH

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='BANLkTik18mT-AYU=myEohquwgJ12hXZzcA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=alan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=shreshthakumar.sahu@stericsson.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).