public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: linux-scsi@vger.kernel.org,
	James Smart <james.smart@avagotech.com>,
	Dick Kennedy <dick.kennedy@avagotech.com>,
	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] lpfc: remove incorrect lockdep assertion
Date: Mon, 18 Apr 2016 09:07:37 +0200	[thread overview]
Message-ID: <1543520.n4UZ9fsgDT@c203> (raw)
In-Reply-To: <20160417132727.000026f3@localhost>

On Sonntag, 17. April 2016 13:27:27 CEST Sebastian Herbszt wrote:
> Remove incorrect lockdep assertion from lpfc_sli_hbqbuf_find() which acquires
> the hbalock itself. Fix the comment which resulted in this mistake.
> 
> Fixes: 1c2ba475eb0e ("lpfc: Add lockdep assertions")
> Signed-off-by: Sebastian Herbszt <herbszt@gmx.de>
> 

Good catch,
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>

-- 
Johannes Thumshirn                                                                                Storage
jthumshirn@suse.de                                                             +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-18  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17 11:27 [PATCH] lpfc: remove incorrect lockdep assertion Sebastian Herbszt
2016-04-18  7:07 ` Johannes Thumshirn [this message]
2016-04-26  2:07 ` Martin K. Petersen

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=1543520.n4UZ9fsgDT@c203 \
    --to=jthumshirn@suse.de \
    --cc=dick.kennedy@avagotech.com \
    --cc=herbszt@gmx.de \
    --cc=james.smart@avagotech.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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