From: Leon Romanovsky <leon@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH v3 0/2] block: Generalize physical entry definition
Date: Sun, 4 Jan 2026 17:15:17 +0200 [thread overview]
Message-ID: <20260104151517.GA563680@unreal> (raw)
In-Reply-To: <20251217-nvme-phys-types-v3-0-f27fd1608f48@nvidia.com>
On Wed, Dec 17, 2025 at 11:41:22AM +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.
Jens,
Can we please progress with this simple series?
Thanks
next prev parent reply other threads:[~2026-01-04 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 9:41 [PATCH v3 0/2] block: Generalize physical entry definition Leon Romanovsky
2025-12-17 9:41 ` [PATCH v3 1/2] nvme-pci: Use size_t for length fields to handle larger sizes Leon Romanovsky
2025-12-17 9:41 ` [PATCH v3 2/2] types: move phys_vec definition to common header Leon Romanovsky
2026-01-04 15:15 ` Leon Romanovsky [this message]
2026-01-06 12:46 ` [PATCH v3 0/2] block: Generalize physical entry definition Jens Axboe
2026-01-07 2:13 ` Jens Axboe
2026-01-07 7:54 ` Leon Romanovsky
2026-01-07 8:29 ` Keith Busch
2026-01-07 15:14 ` Jens Axboe
2026-01-07 15:36 ` Christoph Hellwig
2026-01-07 2:10 ` Jens Axboe
2026-01-14 20:32 ` Alex Williamson
2026-01-18 8:01 ` Leon Romanovsky
2026-01-18 13:28 ` Jens Axboe
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=20260104151517.GA563680@unreal \
--to=leon@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.