From: Bart Van Assche <bvanassche@acm.org>
To: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
quic_cang@quicinc.com, quic_nitirawa@quicinc.com,
avri.altman@wdc.com, beanhuo@micron.com, adrian.hunter@intel.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Peter Wang <peter.wang@mediatek.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Po-Wen Kao <powen.kao@mediatek.com>,
Maramaina Naresh <quic_mnaresh@quicinc.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] scsi: ufs: core: Support Updating UIC Command Timeout
Date: Wed, 22 May 2024 11:16:33 -0700 [thread overview]
Message-ID: <cb05bc3f-5fb0-45aa-961b-bb9edc007407@acm.org> (raw)
In-Reply-To: <292d7702e946ca513af51236ca9e38bf1b1eb269.1716359578.git.quic_nguyenb@quicinc.com>
On 5/22/24 00:01, Bao D. Nguyen wrote:
> interrupt starvations happen occasionally because the uart may
> print long debug messages from different modules in the system.
I think that's a bug in the UART driver that should be fixed in the
UART driver.
Thanks,
Bart.
next prev parent reply other threads:[~2024-05-22 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 7:01 [PATCH v1 0/2] Allow vendor drivers to update UIC command timeout Bao D. Nguyen
2024-05-22 7:01 ` [PATCH v1 1/2] scsi: ufs: core: Support Updating UIC Command Timeout Bao D. Nguyen
2024-05-22 18:16 ` Bart Van Assche [this message]
2024-05-22 20:51 ` Bao D. Nguyen
2024-05-23 4:38 ` Manivannan Sadhasivam
2024-05-23 5:40 ` Bao D. Nguyen
2024-05-22 7:01 ` [PATCH v1 2/2] scsi: ufs: qcom: Update the " Bao D. Nguyen
2024-05-22 18:18 ` Bart Van Assche
2024-05-22 20:56 ` Bao D. Nguyen
2024-05-22 21:01 ` Bart Van Assche
2024-05-23 3:18 ` Avri Altman
2024-05-23 5:42 ` Bao D. Nguyen
2024-05-23 5:34 ` Bao D. Nguyen
2024-05-23 8:17 ` [PATCH v1 0/2] Allow vendor drivers to update UIC command timeout Christoph Hellwig
2024-05-23 14:28 ` Bao D. Nguyen
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=cb05bc3f-5fb0-45aa-961b-bb9edc007407@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=quic_cang@quicinc.com \
--cc=quic_mnaresh@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=stanley.chu@mediatek.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.