[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <000601d9e480$dc0ebb00$942c3100$@samsung.com>
Date: Mon, 11 Sep 2023 16:23:28 +0900
From: "Kiwoong Kim" <kwmad.kim@...sung.com>
To: "'Adrian Hunter'" <adrian.hunter@...el.com>
Cc: <linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<alim.akhtar@...sung.com>, <avri.altman@....com>,
<bvanassche@....org>, <jejb@...ux.ibm.com>, <beanhuo@...ron.com>,
<sc.suh@...sung.com>, <hy50.seo@...sung.com>,
<sh425.lee@...sung.com>, <kwangwon.min@...sung.com>,
<junwoo80.lee@...sung.com>, <wkon.kim@...sung.com>,
"'Martin K. Petersen'" <martin.petersen@...cle.com>
Subject: RE: [RESEND PATCH v3 0/2] change UIC command handling
> > 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.
Powered by blists - more mailing lists