linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Lee Duncan <LDuncan@suse.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	"wubo \(T\)" <wubo40@huawei.com>,
	"cleech\@redhat.com" <cleech@redhat.com>,
	"jejb\@linux.ibm.com" <jejb@linux.ibm.com>,
	"open-iscsi\@googlegroups.com" <open-iscsi@googlegroups.com>,
	"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>,
	Mingfangsen <mingfangsen@huawei.com>,
	"liuzhiqiang \(I\)" <liuzhiqiang26@huawei.com>
Subject: Re: [PATCH V4] scsi: avoid potential deadlock in iscsi_if_rx func
Date: Mon, 09 Dec 2019 20:39:49 -0500	[thread overview]
Message-ID: <yq18snlnel6.fsf@oracle.com> (raw)
In-Reply-To: <ccda52ac-2ea7-b0d2-e36e-08f162569c7c@suse.com> (Lee Duncan's message of "Tue, 10 Dec 2019 00:40:59 +0000")


Lee,

> My sincere apologies. I told wubo I had already reviewed the patch, so
> he didn't need another Reviewed-by from me. I see I was wrong.

OK.

The patch was all mangled so I had to apply the changes by hand. Can't
say that I'm a big fan of retries going negative but I guess that's just
personal taste.

Applied to 5.5/scsi-fixes. Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-12-10  1:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:26 [PATCH V4] scsi: avoid potential deadlock in iscsi_if_rx func wubo (T)
2019-12-07  6:50 ` liuzhiqiang (I)
2019-12-09 23:11 ` Martin K. Petersen
2019-12-10  0:40   ` Lee Duncan
2019-12-10  1:39     ` Martin K. Petersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-30  7:25 wubo (T)

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=yq18snlnel6.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=LDuncan@suse.com \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=cleech@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=liuzhiqiang26@huawei.com \
    --cc=mingfangsen@huawei.com \
    --cc=open-iscsi@googlegroups.com \
    --cc=wubo40@huawei.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).