lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRZBOmQH_pVs93T4@rric.localdomain>
Date: Thu, 13 Nov 2025 21:36:10 +0100
From: Robert Richter <rrichter@....com>
To: Dave Jiang <dave.jiang@...el.com>
Cc: Alison Schofield <alison.schofield@...el.com>,
	Vishal Verma <vishal.l.verma@...el.com>,
	Ira Weiny <ira.weiny@...el.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Jonathan Cameron <jonathan.cameron@...wei.com>,
	Davidlohr Bueso <dave@...olabs.net>, linux-cxl@...r.kernel.org,
	linux-kernel@...r.kernel.org, Gregory Price <gourry@...rry.net>,
	"Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>,
	Terry Bowman <terry.bowman@....com>,
	Joshua Hahn <joshua.hahnjy@...il.com>
Subject: Re: [PATCH 0/3] CXL updates for v6.19

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ