From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Christoph Hellwig <hch@lst.de>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dma-mapping: don't return errors from dma_set_seg_boundary
Date: Thu, 1 Aug 2024 15:33:53 +0200 [thread overview]
Message-ID: <20240801133353.GA1846@lst.de> (raw)
In-Reply-To: <d54f486d-36ae-4668-b314-27137bc4d832@arm.com>
On Thu, Aug 01, 2024 at 01:36:01PM +0100, Robin Murphy wrote:
> I guess I assumed that the old block layer bodges in this area had been
> cleaned up already - perhaps it *is* high time for whatever's left to grow
> a proper understanding of whether a block device actually does its own DMA
> or not.
Can you point to a discussion on that? The concepts here don't make
quite sense to me.
next prev parent reply other threads:[~2024-08-01 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 0:05 remove the dma_set_{max_seg_size,seg_boundary,min_align_mask} return value Christoph Hellwig
2024-07-23 0:05 ` [PATCH 1/3] dma-mapping: don't return errors from dma_set_min_align_mask Christoph Hellwig
2024-07-23 0:05 ` [PATCH 2/3] dma-mapping: don't return errors from dma_set_seg_boundary Christoph Hellwig
2024-08-01 12:00 ` Marek Szyprowski
2024-08-01 12:36 ` Robin Murphy
2024-08-01 13:33 ` Christoph Hellwig [this message]
2024-08-02 11:53 ` Robin Murphy
2024-07-23 0:05 ` [PATCH 3/3] dma-mapping: don't return errors from dma_set_max_seg_size Christoph Hellwig
2024-07-30 13:13 ` remove the dma_set_{max_seg_size,seg_boundary,min_align_mask} return value Robin Murphy
2024-07-30 15:20 ` Christoph Hellwig
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=20240801133353.GA1846@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
/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.