From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
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: Wed, 7 Jan 2026 08:14:07 -0700 [thread overview]
Message-ID: <71e382f7-d6af-4ed6-bc90-4534e4d99792@kernel.dk> (raw)
In-Reply-To: <aV4ZcuXFjN_Eit6v@kbusch-mbp>
On 1/7/26 1:29 AM, Keith Busch wrote:
> On Tue, Jan 06, 2026 at 05:46:21AM -0700, Jens Axboe wrote:
>> On 1/4/26 8:15 AM, Leon Romanovsky wrote:
>>> 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?
>>
>> If Keith/Christoph are happy with it?
>
> Yes, I'm happy with this. Sorry for the delay, I'm still abroad and
> encountered some issues when I should have been holidaying (nothing
> serious, just bad luck), so it's a slow start to the year for me so far.
>
> Acked-by: Keith Busch <kbusch@kernel.org>
OK good, thanks for taking a look. It's all queued up since yesterday.
--
Jens Axboe
next prev parent reply other threads:[~2026-01-07 15:14 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 ` [PATCH v3 0/2] block: Generalize physical entry definition Leon Romanovsky
2026-01-06 12:46 ` 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 [this message]
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=71e382f7-d6af-4ed6-bc90-4534e4d99792@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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 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.