From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH 1/2] serial: bfin_5xx: add missing spin_lock init
Date: Mon, 22 Jun 2009 14:53:31 -0700 [thread overview]
Message-ID: <20090622145331.e6a485df.akpm@linux-foundation.org> (raw)
In-Reply-To: <1244854093-2156-1-git-send-email-vapier@gentoo.org>
On Fri, 12 Jun 2009 20:48:12 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> The Blackfin serial driver never initialized the spin_lock that is part of
> the serial core structure, but we never noticed because spin_lock's are
> rarely enabled on UP systems. Yeah lockdep and friends.
>
I'm sitting here wondering if we need this in -stable, but the changlog
failed to provide sufficient information to determine this.
> drivers/serial/bfin_5xx.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/serial/bfin_5xx.c b/drivers/serial/bfin_5xx.c
> index e2f6b1b..d7fcca1 100644
> --- a/drivers/serial/bfin_5xx.c
> +++ b/drivers/serial/bfin_5xx.c
> @@ -1110,6 +1110,7 @@ static void __init bfin_serial_init_ports(void)
> bfin_serial_hw_init();
>
> for (i = 0; i < nr_active_ports; i++) {
> + spin_lock_init(&bfin_serial_ports[i].port.lock);
> bfin_serial_ports[i].port.uartclk = get_sclk();
> bfin_serial_ports[i].port.fifosize = BFIN_UART_TX_FIFO_SIZE;
> bfin_serial_ports[i].port.ops = &bfin_serial_pops;
It _should_ be possible to do this initialisation at compile-time. But
I expect it would be hard and/or ugly.
prev parent reply other threads:[~2009-06-22 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 0:48 [PATCH 1/2] serial: bfin_5xx: add missing spin_lock init Mike Frysinger
2009-06-13 0:48 ` [PATCH 2/2] serial: bfin_5xx: fix building as module when early printk is enabled Mike Frysinger
2009-06-22 21:54 ` Andrew Morton
2009-06-22 21:53 ` Andrew Morton [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=20090622145331.e6a485df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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