From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] blk-mq: move the DMA mapping code to a separate file
Date: Fri, 16 May 2025 08:43:24 -0600 [thread overview]
Message-ID: <6cc5fdbc-5515-43f6-81ac-b8ab7cc99684@kernel.dk> (raw)
In-Reply-To: <20250516054236.GA13922@lst.de>
On 5/15/25 11:42 PM, Christoph Hellwig wrote:
> Any comments? I was trying to get this out of the way before converting
> the metadata mapping to the iterator.
Code shuffle looks fine, the only thing that's a bit odd is moving the
code and adding the copy right. But it does look like you touched most
of that last, so looks fine. I'll get it applied.
--
Jens Axboe
next prev parent reply other threads:[~2025-05-16 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 7:14 [PATCH 1/2] blk-mq: move the DMA mapping code to a separate file Christoph Hellwig
2025-05-13 7:14 ` [PATCH 2/2] blk-mq: add a copyright notice to blk-mq-dma.c Christoph Hellwig
2025-05-16 5:42 ` [PATCH 1/2] blk-mq: move the DMA mapping code to a separate file Christoph Hellwig
2025-05-16 14:43 ` Jens Axboe [this message]
2025-05-16 14:44 ` 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=6cc5fdbc-5515-43f6-81ac-b8ab7cc99684@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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