> On Feb 18, 2026, at 6:46 PM, Joel Fernandes <[email protected]> wrote: > > Hi, Danilo, > >> On Feb 18, 2026, at 5:24 PM, Danilo Krummrich <[email protected]> wrote: >> >>> On Wed Feb 18, 2026 at 9:54 PM CET, Joel Fernandes wrote: >>> The clist/ffi patches are ready, reviewed by Gary and Danilo. Miguel, can >>> you >>> pull those via the rust tree? >> >> I requested changes in the last version and have yet to go through this one. >> I >> also think that Alex still has some comments (Cc'd him). > > Sure. > >> >> Please note that if this goes through the Rust tree, we have to wait for the >> full upcoming cycle before we can land the GPU buddy abstractions. >> >> Alternatively, if it goes through the Rust tree, Miguel can provide a signed >> tag >> for me to merge or we can simply take it through the drm-rust tree in the >> first >> place, if Miguel agrees with that. > > Ok. > >> >>> The non-Rust DRM buddy related patches are already being pulled into >>> upstream >> >> They are in drm-misc-next, I will merge into drm-rust-next once they hit >> drm-next and -rc1 is out. > > Ok. > >> >>> I will post the nova-core memory management patches as a separate follow-up >>> series just after this one. >>> >>> The git tree with all these patches can be found at: >>> git://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git (tag: nova/mm) >> >> This is now (at least) the third time I have to ask for a patch changelog. >> >> "When sending a next version, add a patch changelog to the cover letter >> or to individual patches explaining difference against previous >> submission (see The canonical patch format)." [1, 2] >> >> Please, add a patch changelog. > > Ah, I think I did not understand what you meant because of my different > interpretation of the words changelog. I have used this term interchangeable > in > the past to summarize what a set of patches do in the cover letter, not what > changed since the last revision. > > Anyway here is a changelog: > > 1. Moving of the clist code to rust ffi > 2. Some comment changes in clist and gpu buddy bindings > 3. Inclusion of the movement of code on C drm buddy.
And to clarify, I’ll go try to include this on a patch by patch basis hence forth in the cover letter as suggested by the documentation. Not just what changed since last time summary. - Joel
