From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: "'Adrian Hunter'" <adrian.hunter@intel.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<bvanassche@acm.org>, <jejb@linux.ibm.com>, <beanhuo@micron.com>,
<sc.suh@samsung.com>, <hy50.seo@samsung.com>,
<sh425.lee@samsung.com>, <kwangwon.min@samsung.com>,
<junwoo80.lee@samsung.com>, <wkon.kim@samsung.com>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>
Subject: RE: [RESEND PATCH v3 0/2] change UIC command handling
Date: Mon, 11 Sep 2023 16:23:28 +0900 [thread overview]
Message-ID: <000601d9e480$dc0ebb00$942c3100$@samsung.com> (raw)
In-Reply-To: <fc40e4f8-6e84-9fbf-e2ca-87330c25c52a@intel.com>
> > static int ufshcd_uic_pwr_ctrl(struct ufs_hba *hba, struct uic_command
> > *cmd) ..
> > bool reenable_intr = false;
> >
> > mutex_lock(&hba->uic_cmd_mutex); <<<<
>
> It is OK to schedule while holding a mutex. Are you sure this is the
> problem?
Ah, I mis-understood it. It was for not applying this.
https://lore.kernel.org/linux-scsi/782ba5f26f0a96e58d85dff50751787d2d2a6b2b.1693790060.git.kwmad.kim@samsung.com/
So this patch set has no problem. Sorry for bothering all of you.
Thanks.
next prev parent reply other threads:[~2023-09-11 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230904014146epcas2p37d6690a5eb3a5652571bb00e358231a3@epcas2p3.samsung.com>
2023-09-04 1:30 ` [RESEND PATCH v3 0/2] change UIC command handling Kiwoong Kim
2023-09-04 1:30 ` [RESEND PATCH v3 1/2] ufs: make __ufshcd_send_uic_cmd not wrapped by host_lock Kiwoong Kim
2023-09-04 8:23 ` Chanwoo Lee
2023-09-04 1:30 ` [RESEND PATCH v3 2/2] ufs: poll HCS.UCRDY before issuing a UIC command Kiwoong Kim
2023-09-04 8:27 ` [RESEND,v3,2/2] " Chanwoo Lee
2023-09-05 10:10 ` [RESEND PATCH v3 0/2] change UIC command handling Martin K. Petersen
2023-09-11 1:35 ` Kiwoong Kim
2023-09-11 5:55 ` Adrian Hunter
2023-09-11 6:32 ` Kiwoong Kim
2023-09-11 7:10 ` Adrian Hunter
2023-09-11 7:23 ` Kiwoong Kim [this message]
[not found] <CGME20230802013848epcas2p3a896970d5bdc8e3f3e422c84c282a151@epcas2p3.samsung.com>
2023-08-02 1:28 ` Kiwoong Kim
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='000601d9e480$dc0ebb00$942c3100$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=junwoo80.lee@samsung.com \
--cc=kwangwon.min@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@samsung.com \
--cc=wkon.kim@samsung.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.