From: Anatoliy Glagolev <glagolig@gmail.com>
To: aglagolev@purestorage.com, adailey@purestorage.com,
jejb@linux.vnet.ibm.com, martin.petersen@oracle.com, hch@lst.de,
qla2xxx-upstream@qlogic.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: qla2xxx: deadlock by configfs_depend_item
Date: Thu, 13 Dec 2018 14:53:11 -0700 [thread overview]
Message-ID: <20181213215310.GA29430@xldev-tmpl.dev.purestorage.com> (raw)
In-Reply-To: <1544140125-3060-1-git-send-email-glagolig@gmail.com>
Any thoughts on this change?
Thanks.
next prev parent reply other threads:[~2018-12-13 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 23:48 [PATCH] scsi: qla2xxx: deadlock by configfs_depend_item Anatoliy Glagolev
2018-12-13 21:53 ` Anatoliy Glagolev [this message]
2018-12-20 2:27 ` 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=20181213215310.GA29430@xldev-tmpl.dev.purestorage.com \
--to=glagolig@gmail.com \
--cc=adailey@purestorage.com \
--cc=aglagolev@purestorage.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qla2xxx-upstream@qlogic.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;
as well as URLs for NNTP newsgroup(s).