public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <rrichter@amd.com>
To: Dave Jiang <dave.jiang@intel.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: Thu, 13 Nov 2025 21:36:10 +0100	[thread overview]
Message-ID: <aRZBOmQH_pVs93T4@rric.localdomain> (raw)
In-Reply-To: <a0881237-60e8-4bd9-b990-b72ad29c57aa@intel.com>

On 13.11.25 13:10:56, Dave Jiang wrote:
> On 11/13/25 9:45 AM, Robert Richter wrote:
> > On 13.11.25 08:20:59, Dave Jiang wrote:
> >> On 11/13/25 4:01 AM, Robert Richter wrote:

> >>> Additionally, patch 3/3 (@inc variable change) of this series also
> >>> depends on patch 02/11 of v5 (store root decoder in in struct
> >>> cxl_region). If you chose to pickup some patches from v5 first on top
> >>> of cxl/next, then all this 3 patches should apply cleanly.
> >>>
> >>> Since 02/11 is one of the first patches and it sounded to me some of
> >>> them will be applied as well, I would prefer that order to avoid
> >>> rebasing and resubmitting a v6 for that. Let me know if you want to
> >>> handle this differently.
> > 
> >> Hmmm....maybe I should just take the entire series hopefully next
> >> cycle when it's ready given all the dependencies?
> > 
> > Patches apply cleanly on top of each other, there is nothing that
> > blocks.
> > 
> > Let me know how to move forward.
> 

> 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.

-Robert

  reply	other threads:[~2025-11-13 20: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 [this message]
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
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=aRZBOmQH_pVs93T4@rric.localdomain \
    --to=rrichter@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@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=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