[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd7f88a8-8e59-464b-ac2d-3c75739076ae@quicinc.com>
Date: Thu, 23 Jan 2025 15:41:20 +0800
From: Ziqi Chen <quic_ziqichen@...cinc.com>
To: Bart Van Assche <bvanassche@....org>, <quic_cang@...cinc.com>,
<mani@...nel.org>, <beanhuo@...ron.com>, <avri.altman@....com>,
<junwoo80.lee@...sung.com>, <martin.petersen@...cle.com>,
<quic_nguyenb@...cinc.com>, <quic_nitirawa@...cinc.com>,
<quic_rampraka@...cinc.com>
CC: <linux-arm-msm@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
Alim Akhtar
<alim.akhtar@...sung.com>,
"James E.J. Bottomley"
<James.Bottomley@...senPartnership.com>,
Peter Wang
<peter.wang@...iatek.com>,
Manivannan Sadhasivam
<manivannan.sadhasivam@...aro.org>,
Andrew Halaney <ahalaney@...hat.com>,
Maramaina Naresh <quic_mnaresh@...cinc.com>,
open list
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 5/8] scsi: ufs: core: Enable multi-level gear scaling
On 1/23/2025 2:32 AM, Bart Van Assche wrote:
> On 1/22/25 2:02 AM, Ziqi Chen wrote:
>> + if (target_gear) {
>> + memcpy(&new_pwr_info, &hba->pwr_info,
>> + sizeof(struct ufs_pa_layer_attr));
>
> Why memcpy() instead of an assignment? The advantage of an assignment is
> that the compiler can perform type checking.
>
> Thanks,
>
> Bart.
>
Hi Bart,
We use memcpy() here is due to memcpy() can be faster than direct
assignment. We don't worry about safety because they are same struct
"ufs_pa_layer_attr" so that we can ensure the accuracy of number of
bytes and member type.
-Ziqi
Powered by blists - more mailing lists