From: Minwoo Im <minwoo.im@samsung.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
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>,
Minwoo Im <minwoo.im@samsung.com>
Subject: Re: [PATCH 2/3] ufs: pci: Add support MCQ for QEMU-based UFS
Date: Sat, 1 Jun 2024 05:54:03 +0900 [thread overview]
Message-ID: <Zlo467UhZ2aAMV0A@localhost> (raw)
In-Reply-To: <6052a799-88c4-4efa-a59e-d560a091a5a0@acm.org>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
On 24-05-31 13:16:40, Bart Van Assche wrote:
> On 5/31/24 03:38, Minwoo Im wrote:
> > +static int ufs_redhat_get_hba_mac(struct ufs_hba *hba)
> > +{
> > + return MAX_SUPP_MAC;
> > +}
>
> Why the prefix "ufs_redhat" instead of "ufs_qemu"?
I thouogh I had to use the same name pattern as ufs_intel_* for the name of
vendor ID of the PCI device. I will update it in the next version.
Thanks for the review.
>
> Thanks,
>
> Bart.
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2024-05-31 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240531104947epcas2p31961bda5ee0eb313c0d9a7d63d5461ba@epcas2p3.samsung.com>
2024-05-31 10:38 ` [PATCH 0/3] ufs: pci: Add support UFSHCI 4.0 MCQ Minwoo Im
2024-05-31 10:38 ` [PATCH 1/3] ufs: mcq: Add ufshcd_mcq_queue_cfg_addr helper Minwoo Im
2024-05-31 20:15 ` Bart Van Assche
2024-05-31 20:55 ` Minwoo Im
2024-05-31 10:38 ` [PATCH 2/3] ufs: pci: Add support MCQ for QEMU-based UFS Minwoo Im
2024-05-31 20:16 ` Bart Van Assche
2024-05-31 20:54 ` Minwoo Im [this message]
2024-05-31 10:38 ` [PATCH 3/3] ufs: mcq: Prevent no I/O queue case for MCQ Minwoo Im
2024-05-31 20:17 ` 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=Zlo467UhZ2aAMV0A@localhost \
--to=minwoo.im@samsung.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--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 \
/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