From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hao Peng <flyingpenghao@gmail.com>
Cc: "jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH ] scsi/ipr: keep the order of locks
Date: Sat, 01 Oct 2022 05:32:56 -0400 [thread overview]
Message-ID: <yq135c7lwlu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAPm50aJ_aW4RmL3_n=5CpGL9D3dXENenFuo5QG0Q2DJO9Gv_1w@mail.gmail.com> (Hao Peng's message of "Fri, 23 Sep 2022 22:51:07 +0800")
> As shown above, there are two lock acquisition order changes. At the
> same time, when ipr_device_reset is executed, the lock hrrq->_lock
> does not need to be held.
Please make sure to copy the driver maintainer when submitting patches:
$ ./scripts/get_maintainer.pl drivers/scsi/ipr.c | head -1
Brian King <brking@us.ibm.com> (supporter:IBM Power Linux RAID adapter)
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-10-01 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:51 [PATCH ] scsi/ipr: keep the order of locks Hao Peng
2022-10-01 9:32 ` Martin K. Petersen [this message]
2022-10-02 4:14 ` Hao Peng
-- strict thread matches above, loose matches on Subject: below --
2022-09-18 2:36 flyingpeng(彭浩)
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=yq135c7lwlu.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=flyingpenghao@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
/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