From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>, 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-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 2/2] types: move phys_vec definition to common header
Date: Sat, 15 Nov 2025 22:25:08 +0000 [thread overview]
Message-ID: <45c46766-2cf4-4e0a-8756-131872ca188b@nvidia.com> (raw)
In-Reply-To: <20251115-nvme-phys-types-v1-2-c0f2e5e9163d@kernel.org>
On 11/15/25 08:22, Leon Romanovsky wrote:
> From: Leon Romanovsky<leonro@nvidia.com>
>
> Move the struct phys_vec definition from block/blk-mq-dma.c to
> include/linux/types.h to make it available for use across the kernel.
>
> The phys_vec structure represents a physical address range with a
> length, which is used by the new physical address-based DMA mapping
> API. This structure is already used by the block layer and will be
> needed for DMA phys API users.
>
> Moving this definition to types.h provides a centralized location
> for this common data structure and eliminates code duplication
> across subsystems that need to work with physical address ranges.
>
> Signed-off-by: Leon Romanovsky<leonro@nvidia.com>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
prev parent reply other threads:[~2025-11-15 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 16:22 [PATCH 0/2] block: Generalize physical entry definition Leon Romanovsky
2025-11-15 16:22 ` [PATCH 1/2] nvme-pci: Use size_t for length fields to handle larger sizes Leon Romanovsky
2025-11-15 17:33 ` David Laight
2025-11-15 18:05 ` Leon Romanovsky
2025-11-15 22:28 ` David Laight
2025-11-16 7:14 ` Leon Romanovsky
2025-11-15 22:25 ` Chaitanya Kulkarni
2025-11-15 16:22 ` [PATCH 2/2] types: move phys_vec definition to common header Leon Romanovsky
2025-11-15 22:25 ` Chaitanya Kulkarni [this message]
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=45c46766-2cf4-4e0a-8756-131872ca188b@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox