From: Bart Van Assche <bvanassche@acm.org>
To: Minwoo Im <minwoo.im@samsung.com>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
gost.dev@samsung.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, Jeuk Kim <jeuk20.kim@samsung.com>
Subject: Re: [PATCH v2 0/2] ufs: pci: Add support UFSHCI 4.0 MCQ
Date: Tue, 4 Jun 2024 16:17:45 -0600 [thread overview]
Message-ID: <6d0e22e7-05af-4f83-8573-bb033c951f72@acm.org> (raw)
In-Reply-To: <20240531212244.1593535-1-minwoo.im@samsung.com>
On 5/31/24 15:22, Minwoo Im wrote:
> This patchset introduces add support for MCQ introduced in UFSHCI 4.0. The
> first patch adds a simple helper to get the address of MCQ queue config
> registers. The second one enables MCQ feature by adding mandatory vops
> callback functions required at MCQ initialization phase. The last one is to
> prevent a case where number of MCQ is given 1 since driver allocates poll_queues
> first rather than I/O queues to handle device commands. Instead of causing
> exception handlers due to no I/O queue, failfast during the initialization time.
For both patches, feel free to add:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2024-06-04 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240531213424epcas2p16d7360e12d310c9f299d449e66af07b3@epcas2p1.samsung.com>
2024-05-31 21:22 ` Minwoo Im
[not found] ` <CGME20240531213425epcas2p2d6291fd4547354afbb067c27b7d1e12f@epcas2p2.samsung.com>
2024-05-31 21:22 ` [PATCH v2 1/2] ufs: pci: Add support MCQ for QEMU-based UFS Minwoo Im
[not found] ` <CGME20240531213425epcas2p477d443427f706b999e81432393bfdc8a@epcas2p4.samsung.com>
2024-05-31 21:22 ` [PATCH v2 2/2] ufs: mcq: Prevent no I/O queue case for MCQ Minwoo Im
2024-06-04 21:25 ` [PATCH v2 0/2] ufs: pci: Add support UFSHCI 4.0 MCQ Minwoo Im
2024-06-04 22:17 ` Bart Van Assche [this message]
2024-06-05 2:17 ` Martin K. Petersen
2024-06-12 1:59 ` Martin K. Petersen
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=6d0e22e7-05af-4f83-8573-bb033c951f72@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=gost.dev@samsung.com \
--cc=jeuk20.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=minwoo.im@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®