From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthias Kaehlcke <matthias@kaehlcke.net>
Cc: Eric.Moore@lsi.com, support@lsi.com, DL-MPTFusionLinux@lsi.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] Fusion MPT: Convert inactive_list_mutex in a mutex
Date: Mon, 05 May 2008 09:26:06 -0500 [thread overview]
Message-ID: <1209997566.3163.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20080504180544.GN20036@traven>
On Sun, 2008-05-04 at 20:05 +0200, Matthias Kaehlcke wrote:
> MPT Fusion: The semaphore inactive_list_mutex is used as a
> mutex. Convert it to the mutex API
>
> Signed-off-by: Matthias Kaehlcke <matthias@kaehlcke.net>
Um, it would at least vaguely help if you checked the tree; even
actually trying to apply the patch would have told you. I know the
email notifications from scsi misc can sometimes get lost.
commit ed5f606fef22e515331aab4c1f927775cf4af70e
Author: Matthias Kaehlcke <matthias@kaehlcke.net>
Date: Sun Mar 9 12:16:27 2008 +0100
[SCSI] mpt fusion: convert inactive_list_mutex to a mutex
James
next prev parent reply other threads:[~2008-05-05 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 18:05 [PATCH] Fusion MPT: Convert inactive_list_mutex in a mutex Matthias Kaehlcke
2008-05-05 14:26 ` James Bottomley [this message]
2008-05-05 15:21 ` Matthias Kaehlcke
2008-05-05 15:28 ` James Bottomley
2008-05-05 15:52 ` Matthias Kaehlcke
-- strict thread matches above, loose matches on Subject: below --
2008-03-09 11:16 [PATCH] Fusion MPT: convert " Matthias Kaehlcke
2008-03-10 15:25 ` Moore, Eric
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=1209997566.3163.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias@kaehlcke.net \
--cc=support@lsi.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