DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=KzydDC7HTP8BAIdjV+QmUM/Vpx0bjs6yWvgrTbjtjRhzVC4HkVGxaAXJCDe/T3kZwD
         0p+e0Kx7oBZMVNGaslKrBhgvZSqOSA5xsODPa2k5AkHuEPEro3NHltd9ibpq8vtFVTGu
         FUpMBEwjh0gJIgmqwA4P/788oY7FPYzIhU1TM=
MIME-Version: 1.0
In-Reply-To: <20090410160137.2f6261ff.akpm@linux-foundation.org>
References: <1239288723-4240-1-git-send-email-abogani@texware.it>
	 <20090410160137.2f6261ff.akpm@linux-foundation.org>
Date: Sat, 11 Apr 2009 17:39:26 +0200
Message-ID: <63a49ef40904110839w53cde9c6k1a261effd1338942@mail.gmail.com>
Subject: Re: [PATCH] tifm: avoid inconsistent lock state
From: Alessio Igor Bogani <abogani@texware.it>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oakad@yahoo.com, linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
       Thomas Gleixner <tglx@linutronix.de>,
       Alan Cox <alan@lxorguk.ukuu.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 577
Lines: 18

Dear Sir Morton,

2009/4/11 Andrew Morton <akpm@linux-foundation.org>:
[...]
> tifm_7xx1_isr() can legitimately use spin_lock() on that lock, because
> it's running in hard IRQ context and "knows" that tifm_7xx1_isr()
> cannot be reentered on this CPU while it is running.
[...]

Thank you for reply and explanation.

Ciao,
Alessio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/