On Tue, Oct 8, 2024, at 11:46, Christoph Hellwig wrote:
On Tue, Oct 08, 2024 at 09:50:09AM +0200, Julian Vetter wrote:
lib/iomap_copy.c | 127 +++++++++++++++++++++++++++++++++++++++
On top of the previous comments: this really should be iomem_copy.c
instead.
Right, I suggested adding it to the existing file since the
functions are logically related, but the naming of that file
identifiers in it is unfortunate:
__iowrite32_copy/__iowrite64_copy/__ioread32_copy sound like
they are meant to work on both IORESOURCE_MEM and IORESOURCE_IO
mappings the same way that iowrite64/ioread64/ioread32 do,
but actually using them on x86 port I/O (from pci_iomap or
ioport_map) would lead to a NULL pointer dereference.
Arnd
