[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9921ee1a-fbe1-4ffe-9490-5cd62714e3ec@linux.ibm.com>
Date: Tue, 4 Mar 2025 11:58:30 +0530
From: Madhavan Srinivasan <maddy@...ux.ibm.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
fbarrat@...ux.ibm.com, ukrishn@...ux.ibm.com, clombard@...ux.ibm.com,
vaibhav@...ux.ibm.com, linuxppc-dev@...ts.ozlabs.org,
Andrew Donnellan <ajd@...ux.ibm.com>
Subject: Re: [PATCH v3 1/1] cxl: Remove driver
On 3/4/25 8:31 AM, Martin K. Petersen wrote:
>
> Hi Madhavan!
>
>> This patch has depenednecy with the first patch
>>
>> https://lists.ozlabs.org/pipermail/linuxppc-dev/2025-February/280990.html
>>
>> Which is already part of your staging tree. Can you please
>> take this patch along with the previous patch.
>
> If I merge the main cxl patch we'll have another conflict due to the
> docs patch below:
>
>>> [0] https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20250219064807.175107-1-ajd@linux.ibm.com/
>
> I don't mind taking both patches but it seems more appropriate for a
> major feature removal like this to go through the relevant architecture
> tree.
>
> Maybe the path of least resistance is for you to put the cxl removal in
> a separate branch and defer sending the pull request until after Linus
> has merged the initial SCSI bits for 6.15?
Yes, I agree and I was thinking of doing it, but wanted to check.
I will send a separate PR after SCSI merge PR.
Thanks for response.
Maddy
>
Powered by blists - more mailing lists