From: David Miller <davem@davemloft.net>
To: socketcan@hartkopp.net
Cc: netdev@vger.kernel.org, socketcan-core@lists.berlios.de,
sam@ravnborg.org
Subject: Re: [PATCH net-next-2.6] can: SJA1000 add missing spin_lock_init()
Date: Thu, 20 May 2010 23:21:55 -0700 (PDT) [thread overview]
Message-ID: <20100520.232155.150173423.davem@davemloft.net> (raw)
In-Reply-To: <4BF415EE.8090307@hartkopp.net>
From: Oliver Hartkopp <socketcan@hartkopp.net>
Date: Wed, 19 May 2010 18:46:38 +0200
> As remarked by Sam Ravnborg the spin_lock variable, that has been introduced
> in commit 57c8a456640fa3ca777652f11f2db4179a3e66b6 ("can: Fix SJA1000 command
> register writes on SMP systems") has not been initialized properly.
>
> This patch adds the initialization to allow spinlock debugging.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Applied, thanks!
prev parent reply other threads:[~2010-05-21 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 16:46 [PATCH net-next-2.6] can: SJA1000 add missing spin_lock_init() Oliver Hartkopp
2010-05-21 6:21 ` David Miller [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=20100520.232155.150173423.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=socketcan-core@lists.berlios.de \
--cc=socketcan@hartkopp.net \
/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).