From: Kumar Gala <galak@kernel.crashing.org>
To: Xiaotian Feng <Xiaotian.Feng@windriver.com>
Cc: linuxppc-dev@ozlabs.org, panto@intracom.gr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpm_uart: fix non-console port startup bug
Date: Mon, 9 Mar 2009 11:46:41 -0500 [thread overview]
Message-ID: <18D6DC29-CCBB-4221-A0B2-64D0555EB8E2@kernel.crashing.org> (raw)
In-Reply-To: <1236308483-20495-1-git-send-email-Xiaotian.Feng@windriver.com>
On Mar 5, 2009, at 9:01 PM, Xiaotian Feng wrote:
> After UART interrupt handler is installed and rx is enabled, if an rx
> interrupt comes before hardware init, rx->cur will be updated. Then
> the
> hardware init will reset BD and make rx->cur out of sync, move the
> hardware
> init code before request_irq.
>
> Signed-off-by: Xiaotian Feng <xiaotian.feng@windriver.com>
> ---
> drivers/serial/cpm_uart/cpm_uart_core.c | 14 ++++++++++++--
> 1 files changed, 12 insertions(+), 2 deletions(-)
applied to next
- k
prev parent reply other threads:[~2009-03-09 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:01 [PATCH] cpm_uart: fix non-console port startup bug Xiaotian Feng
2009-03-09 16:46 ` Kumar Gala [this message]
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=18D6DC29-CCBB-4221-A0B2-64D0555EB8E2@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Xiaotian.Feng@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=panto@intracom.gr \
/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