All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Mike Miller <mike.miller@hp.com>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	iss_storagedev@hp.com, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] cciss: unlock on error path
Date: Fri, 02 Apr 2010 06:39:58 +0000	[thread overview]
Message-ID: <20100402063958.GS23510@kernel.dk> (raw)
In-Reply-To: <20100401155404.GD5265@bicker>

On Thu, Apr 01 2010, Dan Carpenter wrote:
> We take the spin_lock again in fail_all_cmds() so we need to unlock
> here.

Thanks Dan, applied.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Mike Miller <mike.miller@hp.com>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	iss_storagedev@hp.com, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] cciss: unlock on error path
Date: Fri, 2 Apr 2010 08:39:58 +0200	[thread overview]
Message-ID: <20100402063958.GS23510@kernel.dk> (raw)
In-Reply-To: <20100401155404.GD5265@bicker>

On Thu, Apr 01 2010, Dan Carpenter wrote:
> We take the spin_lock again in fail_all_cmds() so we need to unlock
> here.

Thanks Dan, applied.

-- 
Jens Axboe


  parent reply	other threads:[~2010-04-02  6:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 15:54 [patch] cciss: unlock on error path Dan Carpenter
2010-04-01 15:54 ` Dan Carpenter
2010-04-01 16:33 ` scameron
2010-04-01 16:33   ` scameron
2010-04-02  6:39 ` Jens Axboe [this message]
2010-04-02  6:39   ` Jens Axboe

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=20100402063958.GS23510@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=error27@gmail.com \
    --cc=iss_storagedev@hp.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=scameron@beardog.cce.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.