From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Florin Malita <fmalita@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sa1100 serial: sa1100_start_tx spinlock recursion
Date: Sat, 12 Nov 2005 22:10:31 +0000 [thread overview]
Message-ID: <20051112221031.GM28987@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051110220937.4e26592e.fmalita@gmail.com>
On Thu, Nov 10, 2005 at 10:09:37PM -0500, Florin Malita wrote:
> The serial core aquires the port spinlock before calling
> port->ops->start_tx(), so sa1100_start_tx() shouldn't try to lock it
> again.
Applied, thanks.
PS, please do not copy linux-kernel and linux-arm-kernel. The latter
is set for member only posting and it's considered rude to cross post.
Thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-11-12 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 3:09 [PATCH] sa1100 serial: sa1100_start_tx spinlock recursion Florin Malita
2005-11-12 22:10 ` Russell King [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=20051112221031.GM28987@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=fmalita@gmail.com \
--cc=linux-kernel@vger.kernel.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