[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260116101455.45e39650@shazbot.org>
Date: Fri, 16 Jan 2026 10:14:55 -0700
From: Alex Williamson <alex@...zbot.org>
To: Leon Romanovsky <leon@...nel.org>
Cc: linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux.dev, kvm@...r.kernel.org, Sumit Semwal
<sumit.semwal@...aro.org>, Christian König
<christian.koenig@....com>, Jason Gunthorpe <jgg@...pe.ca>, Kevin Tian
<kevin.tian@...el.com>, Joerg Roedel <joro@...tes.org>, Will Deacon
<will@...nel.org>, Robin Murphy <robin.murphy@....com>, Yishai Hadas
<yishaih@...dia.com>, Shameer Kolothum <skolothumtho@...dia.com>, Ankit
Agrawal <ankita@...dia.com>, Matthew Wilcox <willy@...radead.org>, Jens
Axboe <axboe@...nel.dk>
Subject: Re: types: reuse common phys_vec type instead of DMABUF
open‑coded variant
On Wed, 14 Jan 2026 14:18:19 +0200
Leon Romanovsky <leon@...nel.org> wrote:
> On Wed, Jan 07, 2026 at 11:14:14AM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@...dia.com>
> >
> > After commit fcf463b92a08 ("types: move phys_vec definition to common header"),
> > we can use the shared phys_vec type instead of the DMABUF‑specific
> > dma_buf_phys_vec, which duplicated the same structure and semantics.
> >
> > Signed-off-by: Leon Romanovsky <leonro@...dia.com>
> > ---
> > Alex,
> >
> > According to diffstat, VFIO is the subsystem with the largest set of changes,
> > so it would be great if you could take it through your tree.
> >
> > The series is based on the for-7.0/blk-pvec shared branch from Jens:
> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git/log/?h=for-7.0/blk-pvec
> >
> > Thanks
> > ---
>
> Alex,
>
> Could you please move this patch forward? We have the RDMA series [1] that
> depends on this rename, and I would like to base it on the shared branch.
>
> [1] https://lore.kernel.org/all/20260108-dmabuf-export-v1-0-6d47d46580d3@nvidia.com/
I tried to ping Jens regarding why the branch with this code hasn't
been merged into their for-next branch, maybe you have more traction.
Thanks,
Alex
Powered by blists - more mailing lists