From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org, fbarrat@linux.ibm.com,
ukrishn@linux.ibm.com, clombard@linux.ibm.com,
vaibhav@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
Andrew Donnellan <ajd@linux.ibm.com>
Subject: Re: [PATCH v3 1/1] cxl: Remove driver
Date: Mon, 03 Mar 2025 22:01:50 -0500 [thread overview]
Message-ID: <yq1frjttt41.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <9190bfed-8ecd-4941-9297-a8b29c9c47f4@linux.ibm.com> (Madhavan Srinivasan's message of "Mon, 3 Mar 2025 10:37:32 +0530")
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?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-03-04 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 7:00 [PATCH v3 0/1] Remove cxl driver Andrew Donnellan
2025-02-19 7:00 ` [PATCH v3 1/1] cxl: Remove driver Andrew Donnellan
2025-03-03 5:07 ` Madhavan Srinivasan
2025-03-04 3:01 ` Martin K. Petersen [this message]
2025-03-04 6:28 ` Madhavan Srinivasan
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=yq1frjttt41.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=ajd@linux.ibm.com \
--cc=clombard@linux.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=ukrishn@linux.ibm.com \
--cc=vaibhav@linux.ibm.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 NNTP newsgroup(s).