From: simon.kagstrom@netinsight.net (Simon Kagstrom)
To: linux-arm-kernel@lists.infradead.org
Subject: 21285 serial driver deadlock(?) fix
Date: Wed, 13 Jan 2010 09:17:18 +0100 [thread overview]
Message-ID: <20100113091718.10b9a970@marrow.netinsight.se> (raw)
In-Reply-To: <20dd1d411001120912v3d8ec07aofa28282ff10accd8@mail.gmail.com>
On Tue, 12 Jan 2010 20:12:36 +0300
Steve M <stevenm86@gmail.com> wrote:
> I was worried about the regular UART ops wanting a synced version, so I made
> a nonsynced version specifically to be called from the interrupt handler. I
> am attaching that patch for reference.
I'm fine with your patch as well as long as the board doesn't hang at
bootup :-).
Anyway, I belive mine was already applied to Russells git tree:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=5874/1
so I think you'd have to rebase your patch against that and submit it
to the ARM patch system.
// Simon
prev parent reply other threads:[~2010-01-13 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 22:27 21285 serial driver deadlock(?) fix Steve Moskovchenko
2010-01-01 20:29 ` Russell King - ARM Linux
2010-01-04 8:11 ` Simon Kagstrom
[not found] ` <20dd1d411001051037o74fb1187j608889fae0271547@mail.gmail.com>
2010-01-11 9:57 ` Simon Kagstrom
2010-01-12 17:12 ` Steve M
2010-01-13 8:17 ` Simon Kagstrom [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=20100113091718.10b9a970@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=linux-arm-kernel@lists.infradead.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 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).