From: Mike Frysinger <vapier.adi@gmail.com>
To: sonic zhang <sonic.adi@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH][bfin-sport-uart] Walk around RX underflow hardware issue in 32-bit SPORT RX reading
Date: Fri, 18 Sep 2009 11:14:38 -0400 [thread overview]
Message-ID: <8bd0f97a0909180814i1ee3156dj8e2be2763f4eafa1@mail.gmail.com> (raw)
In-Reply-To: <1253264747.22138.2.camel@eight.analog.com>
On Fri, Sep 18, 2009 at 05:05, sonic zhang wrote:
> Disable local interrupts in 32-bit reading from SPORT RX MMR to walk
> around the RX underflow hardware issue when this reading is interrupted
> by the other IRQ.
ive cleaned up the code in svn, so if you want to grab the updated
version for sending out.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
-mike
prev parent reply other threads:[~2009-09-18 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 9:05 [PATCH][bfin-sport-uart] Walk around RX underflow hardware issue in 32-bit SPORT RX reading sonic zhang
2009-09-18 15:14 ` Mike Frysinger [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=8bd0f97a0909180814i1ee3156dj8e2be2763f4eafa1@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sonic.adi@gmail.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).