[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAONX=-fpMBSgMzdY9AnV3iJftv2+0UTiruMiR+Dt_dfwKEd6gA@mail.gmail.com>
Date: Tue, 2 Aug 2022 14:12:07 +1000
From: Daniil Lunev <dlunev@...omium.org>
To: Bart Van Assche <bvanassche@....org>
Cc: Adrian Hunter <adrian.hunter@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Bean Huo <beanhuo@...ron.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Keoseong Park <keosung.park@...sung.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Sohaib Mohamed <sohaib.amhmd@...il.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v5] ufs: core: print UFSHCD capabilities in controller's
sysfs node
> Calling this the effective capabilities of the controller-device pair
> sounds good to me. But please do not refer to hba->caps. I'd like to
> rework hba->caps such that it only includes controller capabilities and
> no information related to the WriteBooster. Additionally, several UFS
> device capabilities that may be exported in the future are not
> represented in hba->caps.
So can you clarify where specifically do you want me to mention that?
Should I name the directory "effective_capabilities" or the commit
message?
Thanks,
--Daniil
Powered by blists - more mailing lists