All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: bvanassche@acm.org
Cc: "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>,
	<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>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] scsi: ufs: core: Support Updating UIC Command Timeout
Date: Tue, 11 Jun 2024 21:43:56 -0400	[thread overview]
Message-ID: <yq17cevym2d.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <f3fded35cb250e16ee5aaa67d7a7288fe2799fd7.1717104518.git.quic_nguyenb@quicinc.com> (Bao D. Nguyen's message of "Thu, 30 May 2024 14:36:40 -0700")


Hi Bart!

> Add support for overriding the UIC command timeout value with the
> newly created uic_cmd_timeout kernel module parameter. Default value
> is 500ms. Supported values range from 500ms to 2 seconds.
>
> Signed-off-by: Bao D. Nguyen <quic_nguyenb@quicinc.com>
> Suggested-by: Bart Van Assche <bvanassche@acm.org>

You requested changes which means you are on the hook for a review...

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2024-06-12  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 21:36 [PATCH v2 0/1] Allow platform drivers to update UIC command timeout Bao D. Nguyen
2024-05-30 21:36 ` [PATCH v2 1/1] scsi: ufs: core: Support Updating UIC Command Timeout Bao D. Nguyen
2024-06-12  1:43   ` Martin K. Petersen [this message]
2024-06-12  3:25     ` Bart Van Assche
2024-06-12  3:24   ` Bart Van Assche

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=yq17cevym2d.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.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=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=peter.wang@mediatek.com \
    --cc=quic_cang@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.