[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221113163535.884299-1-hch@lst.de>
Date: Sun, 13 Nov 2022 17:35:28 +0100
From: Christoph Hellwig <hch@....de>
To: Dennis Dalessandro <dennis.dalessandro@...nelisnetworks.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Alexandra Winter <wintera@...ux.ibm.com>,
Wenjia Zhang <wenjia@...ux.ibm.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Russell King <linux@...linux.org.uk>,
Robin Murphy <robin.murphy@....com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-rdma@...r.kernel.org,
iommu@...ts.linux.dev, linux-media@...r.kernel.org,
netdev@...r.kernel.org, linux-s390@...r.kernel.org,
alsa-devel@...a-project.org
Subject: stop drivers from passing GFP_COMP to dma_alloc_coherent
Hi all,
this series fixes up various drivers that either try to get a compound
page from dma_alloc_coherent or more often just did a bit of cargo
cult copy and paste, and then warns about this flag passed in the
DMA layer instead of silently clearing it like done by ARM and dma-iommu
before.
Diffstat:
arch/arm/mm/dma-mapping.c | 17 -----------------
drivers/infiniband/hw/hfi1/init.c | 21 +++------------------
drivers/infiniband/hw/qib/qib_iba6120.c | 2 +-
drivers/infiniband/hw/qib/qib_init.c | 21 ++++-----------------
drivers/iommu/dma-iommu.c | 3 ---
drivers/media/v4l2-core/videobuf-dma-contig.c | 22 ++++++++--------------
drivers/net/ethernet/broadcom/cnic.c | 6 ++----
drivers/s390/net/ism_drv.c | 3 ++-
kernel/dma/mapping.c | 8 ++++++++
sound/core/memalloc.c | 5 ++---
10 files changed, 30 insertions(+), 78 deletions(-)
Powered by blists - more mailing lists