From: Clemens Buchacher <drizzd@aon.at>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [7/7] LEON SPARC V8 processor support for linux-2.6.10
Date: Sun, 9 Jan 2005 10:36:18 +0100 [thread overview]
Message-ID: <20050109093618.GA25465@kzelldran.lan> (raw)
In-Reply-To: <41DAE8CC.3010904@gaisler.com>
On Tue, Jan 04, 2005 at 08:04:44PM +0100, Jiri Gaisler wrote:
> +static irqreturn_t leonuart_int(int irq, void *dev_id, struct pt_regs *regs)
> +{
> + struct uart_port *port = dev_id;
> + unsigned int status;
> +
> + spin_lock(port ->lock);
I think that should be
spin_lock(&port->lock);
[...]
> + spin_unlock(port ->lock);
and
spin_unlock(&port->lock);
> + return IRQ_HANDLED;
> +}
Regards,
Clemens
prev parent reply other threads:[~2005-01-09 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 19:04 [7/7] LEON SPARC V8 processor support for linux-2.6.10 Jiri Gaisler
2005-01-04 19:22 ` Roland Dreier
2005-01-05 0:01 ` Alan Cox
2005-01-05 15:19 ` Jiri Gaisler
2005-01-06 12:41 ` Alan Cox
2005-01-09 9:36 ` Clemens Buchacher [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=20050109093618.GA25465@kzelldran.lan \
--to=drizzd@aon.at \
--cc=jiri@gaisler.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).