From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, John Crispin <john@phrozen.org>,
Vinod Koul <vkoul@kernel.org>,
Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org,
alsa-devel@alsa-project.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH 10/18] smc911x: pass struct device to DMA API functions
Date: Fri, 1 Feb 2019 17:11:16 +0100 [thread overview]
Message-ID: <20190201161116.GG6532@lst.de> (raw)
In-Reply-To: <a8653acc-e0db-69a1-a8d3-2190f3767ce3@arm.com>
On Fri, Feb 01, 2019 at 02:14:34PM +0000, Robin Murphy wrote:
> And equivalently for rxdma here. However, given that this all seems only
> relevant to antique ARCH_PXA platforms which are presumably managing to
> work as-is, it's probably not worth tinkering too much. I'd just stick a
> note in the commit message that we're still only making these
> self-consistent with the existing dma_map_single() calls rather than
> necessarily correct.
Sounds good.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, John Crispin <john@phrozen.org>,
Vinod Koul <vkoul@kernel.org>,
Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org,
alsa-devel@alsa-project.org, iommu@lists.linux-foundation.org
Subject: [10/18] smc911x: pass struct device to DMA API functions
Date: Fri, 1 Feb 2019 17:11:16 +0100 [thread overview]
Message-ID: <20190201161116.GG6532@lst.de> (raw)
On Fri, Feb 01, 2019 at 02:14:34PM +0000, Robin Murphy wrote:
> And equivalently for rxdma here. However, given that this all seems only
> relevant to antique ARCH_PXA platforms which are presumably managing to
> work as-is, it's probably not worth tinkering too much. I'd just stick a
> note in the commit message that we're still only making these
> self-consistent with the existing dma_map_single() calls rather than
> necessarily correct.
Sounds good.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, John Crispin <john@phrozen.org>,
Vinod Koul <vkoul@kernel.org>,
Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org,
alsa-devel@alsa-project.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH 10/18] smc911x: pass struct device to DMA API functions
Date: Fri, 01 Feb 2019 16:11:16 +0000 [thread overview]
Message-ID: <20190201161116.GG6532@lst.de> (raw)
In-Reply-To: <a8653acc-e0db-69a1-a8d3-2190f3767ce3@arm.com>
On Fri, Feb 01, 2019 at 02:14:34PM +0000, Robin Murphy wrote:
> And equivalently for rxdma here. However, given that this all seems only
> relevant to antique ARCH_PXA platforms which are presumably managing to
> work as-is, it's probably not worth tinkering too much. I'd just stick a
> note in the commit message that we're still only making these
> self-consistent with the existing dma_map_single() calls rather than
> necessarily correct.
Sounds good.
next prev parent reply other threads:[~2019-02-01 16:11 UTC|newest]
Thread overview: 125+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 8:47 don't pass a NULL struct device to DMA API functions Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [PATCH 01/18] MIPS: lantiq: pass " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [01/18] " Christoph Hellwig
2019-02-07 23:29 ` [PATCH 01/18] " Paul Burton
2019-02-07 23:29 ` Paul Burton
2019-02-07 23:29 ` [01/18] " Paul Burton
2019-02-12 7:45 ` [PATCH 01/18] " Christoph Hellwig
2019-02-12 7:45 ` Christoph Hellwig
2019-02-12 7:45 ` [01/18] " Christoph Hellwig
2019-02-12 17:41 ` [PATCH 01/18] " Paul Burton
2019-02-12 17:41 ` Paul Burton
2019-02-12 17:41 ` [01/18] " Paul Burton
2019-02-01 8:47 ` [PATCH 02/18] dmaengine: imx-sdma: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [02/18] " Christoph Hellwig
2019-02-02 10:11 ` [PATCH 02/18] " Vinod Koul
2019-02-02 10:23 ` Vinod Koul
2019-02-02 10:11 ` [02/18] " Vinod Koul
2019-02-02 17:21 ` [PATCH 02/18] " Christoph Hellwig
2019-02-02 17:21 ` Christoph Hellwig
2019-02-02 17:21 ` [02/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 03/18] net: caif: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [03/18] " Christoph Hellwig
2019-02-01 13:53 ` [PATCH 03/18] " Robin Murphy
2019-02-01 13:53 ` Robin Murphy
2019-02-01 13:53 ` [03/18] " Robin Murphy
2019-02-01 16:10 ` [PATCH 03/18] " Christoph Hellwig
2019-02-01 16:10 ` Christoph Hellwig
2019-02-01 16:10 ` [03/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 04/18] au1000_eth: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [04/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 05/18] macb_main: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [05/18] " Christoph Hellwig
2019-02-01 13:34 ` [PATCH 05/18] " Nicolas.Ferre
2019-02-01 13:34 ` Nicolas.Ferre
2019-02-01 13:34 ` Nicolas.Ferre
2019-02-01 13:34 ` [05/18] " Nicolas Ferre
2019-02-01 8:47 ` [PATCH 06/18] lantiq_etop: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [06/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 07/18] pxa168_eth: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [07/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 08/18] moxart_ether: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [08/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 09/18] meth: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [09/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 10/18] smc911x: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [10/18] " Christoph Hellwig
2019-02-01 14:14 ` [PATCH 10/18] " Robin Murphy
2019-02-01 14:14 ` Robin Murphy
2019-02-01 14:14 ` [10/18] " Robin Murphy
2019-02-01 16:11 ` Christoph Hellwig [this message]
2019-02-01 16:11 ` [PATCH 10/18] " Christoph Hellwig
2019-02-01 16:11 ` [10/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 11/18] parport_ip32: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [11/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 12/18] fotg210-udc: remove a bogus dma_sync_single_for_device call Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [12/18] " Christoph Hellwig
2019-02-01 13:19 ` [PATCH 12/18] " Felipe Balbi
2019-02-01 13:19 ` Felipe Balbi
2019-02-01 13:19 ` [12/18] " Felipe Balbi
2019-02-01 16:10 ` [PATCH 12/18] " Christoph Hellwig
2019-02-01 16:10 ` Christoph Hellwig
2019-02-01 16:10 ` [12/18] " Christoph Hellwig
2019-02-11 13:12 ` [PATCH 12/18] " Christoph Hellwig
2019-02-11 13:12 ` Christoph Hellwig
2019-02-11 13:12 ` [12/18] " Christoph Hellwig
2019-02-11 13:30 ` [PATCH 12/18] " Felipe Balbi
2019-02-11 13:30 ` Felipe Balbi
2019-02-11 13:30 ` Felipe Balbi
2019-02-11 13:30 ` [12/18] " Felipe Balbi
2019-02-01 8:47 ` [PATCH 13/18] fotg210-udc: pass struct device to DMA API functions Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [13/18] " Christoph Hellwig
2019-02-01 13:20 ` [PATCH 13/18] " Felipe Balbi
2019-02-01 13:20 ` Felipe Balbi
2019-02-01 13:20 ` [13/18] " Felipe Balbi
2019-02-01 8:47 ` [PATCH 14/18] da8xx-fb: " Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [14/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 15/18] gbefb: switch to managed version of the DMA allocator Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [15/18] " Christoph Hellwig
2019-02-01 8:47 ` [PATCH 16/18] pxa3xx-gcu: pass struct device to dma_mmap_coherent Christoph Hellwig
2019-02-01 8:47 ` Christoph Hellwig
2019-02-01 8:47 ` [16/18] " Christoph Hellwig
2019-02-01 8:48 ` [PATCH 17/18] ALSA: hal2: pass struct device to DMA API functions Christoph Hellwig
2019-02-01 8:48 ` Christoph Hellwig
2019-02-01 8:48 ` [17/18] " Christoph Hellwig
2019-02-01 13:12 ` [alsa-devel] [PATCH 17/18] " Takashi Iwai
2019-02-01 13:12 ` Takashi Iwai
2019-02-01 13:12 ` [17/18] " Takashi Iwai
2019-02-01 16:09 ` [alsa-devel] [PATCH 17/18] " Christoph Hellwig
2019-02-01 16:09 ` Christoph Hellwig
2019-02-01 16:09 ` [17/18] " Christoph Hellwig
2019-02-01 16:17 ` [alsa-devel] [PATCH 17/18] " Takashi Iwai
2019-02-01 16:17 ` Takashi Iwai
2019-02-01 16:17 ` [17/18] " Takashi Iwai
2019-02-01 8:48 ` [PATCH 18/18] ALSA: " Christoph Hellwig
2019-02-01 8:48 ` Christoph Hellwig
2019-02-01 8:48 ` [18/18] " Christoph Hellwig
2019-02-01 13:13 ` [alsa-devel] [PATCH 18/18] " Takashi Iwai
2019-02-01 13:13 ` Takashi Iwai
2019-02-01 13:13 ` [18/18] " Takashi Iwai
2019-02-01 13:16 ` [alsa-devel] don't pass a NULL " Takashi Iwai
2019-02-01 13:16 ` Takashi Iwai
2019-02-01 13:16 ` Takashi Iwai
2019-02-01 16:09 ` Christoph Hellwig
2019-02-01 16:09 ` [alsa-devel] " Christoph Hellwig
2019-02-01 16:09 ` Christoph Hellwig
2019-02-01 16:09 ` Christoph Hellwig
2019-02-01 16:18 ` Takashi Iwai
2019-02-01 16:18 ` Takashi Iwai
2019-02-01 16:18 ` Takashi Iwai
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=20190201161116.GG6532@lst.de \
--to=hch@lst.de \
--cc=alsa-devel@alsa-project.org \
--cc=balbi@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.tarnyagin@lockless.no \
--cc=iommu@lists.linux-foundation.org \
--cc=john@phrozen.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robin.murphy@arm.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=vkoul@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 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.