Re: [PATCH v3 0/2] block: Generalize physical entry definition

From: Alex Williamson

Date: Wed Jan 14 2026 - 15:32:45 EST


On Tue, 06 Jan 2026 19:10:46 -0700
Jens Axboe <axboe@xxxxxxxxx> wrote:

> On Wed, 17 Dec 2025 11:41:22 +0200, Leon Romanovsky wrote:
> > Jens,
> >
> > I would like to ask you to put these patches on some shared branch based
> > on v6.19-rcX tag, so I will be able to reuse this general type in VFIO
> > and DMABUF code.
> >
> > --------------------------------------------------------------------------------
> > Changelog:
> > v3:
> > * Rebased on top v6.19-rc1
> > * Added note that memory size is not changed despite change in the
> > variable type.
> > v2: https://lore.kernel.org/linux-nvme/20251117-nvme-phys-types-v2-0-c75a60a2c468@xxxxxxxxxx/
> > * Added Chaitanya's Reviewed-by tags.
> > * Removed explicit casting from size_t to unsigned int.
> > v1: https://patch.msgid.link/20251115-nvme-phys-types-v1-0-c0f2e5e9163d@xxxxxxxxxx
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] nvme-pci: Use size_t for length fields to handle larger sizes
> commit: 073b9bf9af463d32555c5ebaf7e28c3a44c715d0
> [2/2] types: move phys_vec definition to common header
> commit: fcf463b92a08686d1aeb1e66674a72eb7a8bfb9b

Hi Jens,

I see this is currently on your for-7.0/blk-pvec branch, thanks for
splitting it out. I haven't seen this merged into your for-next branch
though, which gives me some pause merging it for a dependent series
from Leon. Is there anything blocking that merge? Thanks,

Alex