From: David Miller <davem@davemloft.net>
To: rmk@arm.linux.org.uk
Cc: u.kleine-koenig@pengutronix.de, srostedt@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] am79c961a: fix spin_lock usage
Date: Thu, 22 Jan 2009 16:16:59 -0800 (PST) [thread overview]
Message-ID: <20090122.161659.261404462.davem@davemloft.net> (raw)
In-Reply-To: <20090122234036.GA23484@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Thu, 22 Jan 2009 23:40:36 +0000
> On Thu, Jan 22, 2009 at 02:56:15PM -0800, David Miller wrote:
> > From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > Date: Thu, 22 Jan 2009 23:29:42 +0100
> >
> > > spin_lock functions take a pointer to the lock, not the lock itself.
> > > This error was noticed by compiling ebsa110_defconfig for linux-rt where
> > > the locking functions obviously are more picky about their arguments.
> > >
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >
> > Russell, this fix is real. Want me to take it or will you?
>
> I'll take it.
Great.
> > BTW, I took linux-arm-kernel out of the CC because all of my postings
> > there bounce simply because I lack reverse DNS :-/
>
> No need; in theory I've whitelisted your IP. However, I've dropped
> 12o3l@tiscali.nl from the CC because that address bounces.
Thanks, I noticed him bounce too.
prev parent reply other threads:[~2009-01-23 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 22:29 [PATCH] am79c961a: fix spin_lock usage Uwe Kleine-König
2009-01-22 22:34 ` Russell King - ARM Linux
2009-01-22 22:44 ` Uwe Kleine-König
2009-01-23 20:43 ` Robert Schwebel
2009-01-23 21:15 ` Uwe Kleine-König
2009-01-22 22:56 ` David Miller
2009-01-22 23:40 ` Russell King
2009-01-23 0:16 ` 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=20090122.161659.261404462.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=srostedt@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).