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>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Joel Granados <j.granados@samsung.com>,
gost.dev@samsung.com, Asutosh Das <quic_asutoshd@quicinc.com>
Subject: Re: [PATCH v2 2/2] ufs: mcq: Convert MCQ_CFG_n to a inline function
Date: Mon, 20 May 2024 11:17:54 -0700 [thread overview]
Message-ID: <84c1e98d-1217-4956-909f-d51fdf2f555e@acm.org> (raw)
In-Reply-To: <20240519221457.772346-3-minwoo.im@samsung.com>
On 5/19/24 15:14, Minwoo Im wrote:
> Unlike the previous patch, this patch does not fix any issues, but,
> inline functions are much more preferred over macros, so this patch
> converted MCQ_CFG_n macro in ufs-mcq to an inline function along with
> the previous patch.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2024-05-20 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240519222604epcas2p3d427f2f5b3b0156881f6840443210931@epcas2p3.samsung.com>
2024-05-19 22:14 ` [PATCH v2 0/2] ufs: mcq: Fix and cleanup unsafe macros Minwoo Im
[not found] ` <CGME20240519222606epcas2p45c250e92bacb3aa0b00f7430ee69884d@epcas2p4.samsung.com>
2024-05-19 22:14 ` [PATCH v2 1/2] ufs: mcq: Fix missing argument 'hba' in MCQ_OPR_OFFSET_n Minwoo Im
2024-05-20 18:17 ` Bart Van Assche
[not found] ` <CGME20240519222607epcas2p1c485b3cc264fdabc2c1e90daf228664d@epcas2p1.samsung.com>
2024-05-19 22:14 ` [PATCH v2 2/2] ufs: mcq: Convert MCQ_CFG_n to a inline function Minwoo Im
2024-05-20 18:17 ` Bart Van Assche [this message]
2024-05-31 0:46 ` [PATCH v2 0/2] ufs: mcq: Fix and cleanup unsafe macros 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=84c1e98d-1217-4956-909f-d51fdf2f555e@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=j.granados@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=minwoo.im@samsung.com \
--cc=quic_asutoshd@quicinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).