public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: openib-general@openib.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix potential deadlock in mthca
Date: Fri, 11 Aug 2006 09:15:48 -0700	[thread overview]
Message-ID: <44DCAD34.5040502@linux.intel.com> (raw)
In-Reply-To: <adad5b7ntyh.fsf@cisco.com>

Roland Dreier wrote:
> Here's a long-standing bug that lockdep found very nicely.
> 
> Ingo/Arjan, can you confirm that the fix looks OK and I am using
> spin_lock_nested() properly?  I couldn't find much documentation or
> many examples of it, so I'm not positive this is the right way to
> handle this fix.
> 

looks correct to me;

Acked-by: Arjan van de Ven <arjan@linux.intel.com>

  reply	other threads:[~2006-08-11 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 16:00 [PATCH] Fix potential deadlock in mthca Roland Dreier
2006-08-11 16:15 ` Arjan van de Ven [this message]
2006-08-14 11:07   ` Ingo Molnar

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=44DCAD34.5040502@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.com \
    /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