From: Dave Jiang <dave.jiang@intel.com>
To: Robert Richter <rrichter@amd.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Davidlohr Bueso <dave@stgolabs.net>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory Price <gourry@gourry.net>,
"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>,
Terry Bowman <terry.bowman@amd.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>
Subject: Re: [PATCH 0/3] CXL updates for v6.19
Date: Fri, 14 Nov 2025 11:35:51 -0700 [thread overview]
Message-ID: <be005f26-3514-4870-a203-73813290f93d@intel.com> (raw)
In-Reply-To: <aRd0K1MGNGUduYBC@rric.localdomain>
On 11/14/25 11:25 AM, Robert Richter wrote:
> On 14.11.25 11:18:23, Dave Jiang wrote:
>>
>>
>> On 11/14/25 9:28 AM, Dave Jiang wrote:
>>>
>>>
>>> On 11/14/25 9:21 AM, Robert Richter wrote:
>>>> On 14.11.25 08:32:00, Dave Jiang wrote:
>>>>>
>>>>>
>>>>> On 11/14/25 2:09 AM, Robert Richter wrote:
>>>>>> On 13.11.25 21:36:16, Robert Richter wrote:
>>>>>>> On 13.11.25 13:10:56, Dave Jiang wrote:
>>>>>>>> On 11/13/25 9:45 AM, Robert Richter wrote:
>>>>>>
>>>>>>>> So currently we want to apply the 3 patches ahead of time right? Can
>>>>>>>> you 1. post the series against 6.18-rc5, 2. provide a public branch
>>>>>>>> (github or kernel.org) that merged this branch with cxl/next (given
>>>>>>>> there are expected complications) that I can reference? That's
>>>>>>>> really my preference.
>>>>>>>
>>>>>>> Ok, thanks.
>>>>>>
>>>>>> I sent you a delta patch as I don't have a public git tree at hand
>>>>>> right now.
>>>>
>>>>> That works. Have you sent it yet? I don't think I've received it. Or
>>>>> I can give you push permission to my github repo if you can give me
>>>>> your github user name.
>>>>
>>>> See here:
>>>>
>>>> https://patchwork.kernel.org/project/cxl/patch/20251114090532.1323361-1-rrichter@amd.com/
>>>>
>>>> -Robert
>>>
>>> Oh this is merge patch for the entire series. I thought it's just the 3 patches since we are merging those ahead of time while waiting for the rest of the series to be ready?
>>>
>>>
>> Robert,
>> Can you please verify that this merge looks correct to you? Thanks!
>> https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/log/?h=next-6.19-merge-prm-prep
>>
>
> Yes, same what I have. Thanks.
>
> I am going to send v7 with an update of the comment of patch 11/11
> (decoder lock).
You can use for-6.19/cxl-prm as base. I have pushed it to the cxl git.>
> -Robert
next prev parent reply other threads:[~2025-11-14 18:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 20:51 [PATCH 0/3] CXL updates for v6.19 Robert Richter
2025-11-12 20:51 ` [PATCH 1/3] cxl: Simplify cxl_rd_ops allocation and handling Robert Richter
2025-11-12 22:35 ` Gregory Price
2025-11-12 20:51 ` [PATCH 2/3] cxl/acpi: Group xor arithmetric setup code in a single block Robert Richter
2025-11-12 22:36 ` Gregory Price
2025-11-12 22:38 ` Gregory Price
2025-11-12 20:51 ` [PATCH 3/3] cxl/region: Remove local variable @inc in cxl_port_setup_targets() Robert Richter
2025-11-12 22:40 ` Gregory Price
2025-11-12 21:45 ` [PATCH 0/3] CXL updates for v6.19 Dave Jiang
2025-11-13 11:01 ` Robert Richter
2025-11-13 15:20 ` Dave Jiang
2025-11-13 15:32 ` Gregory Price
2025-11-13 16:34 ` Dave Jiang
2025-11-13 16:45 ` Robert Richter
2025-11-13 20:10 ` Dave Jiang
2025-11-13 20:36 ` Robert Richter
2025-11-14 9:09 ` Robert Richter
2025-11-14 15:32 ` Dave Jiang
2025-11-14 16:21 ` Robert Richter
2025-11-14 16:28 ` Dave Jiang
2025-11-14 18:18 ` Dave Jiang
2025-11-14 18:25 ` Robert Richter
2025-11-14 18:35 ` Dave Jiang [this message]
2025-11-14 20:19 ` Dave Jiang
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=be005f26-3514-4870-a203-73813290f93d@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fabio.m.de.francesco@linux.intel.com \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.com \
--cc=vishal.l.verma@intel.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