From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: cleanup ->dma_configure calling conventions
Date: Mon, 27 Aug 2018 10:47:07 +0200 [thread overview]
Message-ID: <20180827084711.23407-1-hch@lst.de> (raw)
Hi all,
this series cleans up a bit how we call ->dma_configure and how
we clean up after tearing down a device that the method did set
up.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: cleanup ->dma_configure calling conventions
Date: Mon, 27 Aug 2018 10:47:07 +0200 [thread overview]
Message-ID: <20180827084711.23407-1-hch@lst.de> (raw)
Hi all,
this series cleans up a bit how we call ->dma_configure and how
we clean up after tearing down a device that the method did set
up.
next reply other threads:[~2018-08-27 8:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 8:47 Christoph Hellwig [this message]
2018-08-27 8:47 ` cleanup ->dma_configure calling conventions Christoph Hellwig
2018-08-27 8:47 ` [PATCH 1/4] arm-nommu: don't define arch_teardown_dma_ops Christoph Hellwig
2018-08-27 8:47 ` Christoph Hellwig
2018-08-27 8:47 ` Christoph Hellwig
2018-09-06 12:11 ` Robin Murphy
2018-09-06 12:11 ` Robin Murphy
2018-09-11 10:23 ` Vladimir Murzin
2018-09-11 10:23 ` Vladimir Murzin
2018-08-27 8:47 ` [PATCH 2/4] dma-mapping: remove dma_configure Christoph Hellwig
2018-08-27 8:47 ` Christoph Hellwig
2018-09-06 12:14 ` Robin Murphy
2018-09-06 12:14 ` Robin Murphy
2018-08-27 8:47 ` [PATCH 3/4] dma-mapping: remove dma_deconfigure Christoph Hellwig
2018-08-27 8:47 ` Christoph Hellwig
2018-09-06 12:19 ` Robin Murphy
2018-09-06 12:19 ` Robin Murphy
2018-08-27 8:47 ` [PATCH 4/4] dma-mapping: clear dev->dma_ops in arch_teardown_dma_ops Christoph Hellwig
2018-08-27 8:47 ` Christoph Hellwig
2018-09-06 12:20 ` Robin Murphy
2018-09-06 12:20 ` Robin Murphy
2018-09-22 15:01 ` Guenter Roeck
2018-09-22 15:01 ` Guenter Roeck
2018-09-25 5:32 ` Michael Ellerman
2018-09-25 5:32 ` Michael Ellerman
2018-09-25 20:16 ` Christoph Hellwig
2018-09-25 20:16 ` Christoph Hellwig
2018-09-26 4:20 ` Michael Ellerman
2018-09-26 4:20 ` Michael Ellerman
2018-09-26 4:20 ` Michael Ellerman
2018-09-26 10:45 ` Robin Murphy
2018-09-26 10:45 ` Robin Murphy
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=20180827084711.23407-1-hch@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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.