[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7b513cc3-b218-fe57-1d24-6a10b225b6da@quicinc.com>
Date: Mon, 12 Sep 2022 11:18:57 -0700
From: "Asutosh Das (asd)" <quic_asutoshd@...cinc.com>
To: Bart Van Assche <bvanassche@....org>, <quic_nguyenb@...cinc.com>,
<quic_xiaosenh@...cinc.com>, <stanley.chu@...iatek.com>,
<adrian.hunter@...el.com>, <avri.altman@....com>,
<mani@...nel.org>, <quic_cang@...cinc.com>, <beanhuo@...ron.com>,
<martin.petersen@...cle.com>, <linux-scsi@...r.kernel.org>
CC: <linux-arm-msm@...r.kernel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v3 1/4] ufs: core: prepare ufs for multi circular
queue support
On 9/9/2022 4:38 PM, Bart Van Assche wrote:
> On 9/9/22 15:48, Asutosh Das (asd) wrote:
>> Hello Bart,
>> Thanks for the comments.
>>
>> On 9/8/2022 2:58 PM, Bart Van Assche wrote:
>>> On 9/2/22 15:41, Asutosh Das wrote:
>>>> Preparatory changes for upcoming multi circular queue.
>>>
>>> One patch per change please and also describe each individual change.
>>> From
>>> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#split-changes: "Separate each logical change into a separate patch".
>>>
>> The intent of this change was to have all the non-mcq related changes
>> to the ufshcd as a separate patch.
>> I would add more details to the commit message of this change.
>> If there's anything specific in this patch that may need changes,
>> please let me know.
>
> Please follow the "one change per patch" rule. This is a widely followed
> rule in the Linux kernel community. This rule exists because it is the
> responsibility of the developer(s) who post a patch series to make it
> easy for reviewers to review their work.
>
Let me review and restructure the code and push it again.
I would like to remove the RFC tag in the next version.
Please let me know if that's _not_ OK.
> Thanks,
>
> Bart.
Powered by blists - more mailing lists