linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-doc@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	linux-kernel@vger.kernel.org,
	James Bottomley <jbottomley@parallels.com>,
	linux-pci@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3 0/4] Clean up DMA API docs and dma_addr_t usage
Date: Wed, 14 May 2014 12:23:07 +0200	[thread overview]
Message-ID: <20140514102307.GD6026@8bytes.org> (raw)
In-Reply-To: <20140508204257.17877.4639.stgit@bhelgaas-glaptop.roam.corp.google.com>

On Thu, May 08, 2014 at 02:48:47PM -0600, Bjorn Helgaas wrote:
> Maybe the third time's a charm :)
> 
> This cleans up some DMA-API documentation and makes a minor no-op change to
> the dma_declare_coherent_memory() prototype.
> 
> Changes from v2:
>   - Added description of CPU virtual/physical and bus addresses in
>     DMA-API-HOWTO
>   - Added comments to sh/PCI (Dreamcast) update
>   - Dropped IOMMU interface dma_addr_t changes
> 
> I didn't add Arnd's and Greg's acks to patch 1 because of all the new
> address description text I added.
> 
> ---
> 
> Bjorn Helgaas (4):
>       DMA-API: Clarify physical/bus address distinction
>       DMA-API: Change dma_declare_coherent_memory() CPU address to phys_addr_t
>       sh/PCI: Pass GAPSPCI_DMA_BASE CPU & bus address to dma_declare_coherent_memory()
>       iommu/exynos: Remove unnecessary "&" from function pointers

Applied patches 1-3 to my core branch and patch 4 to the arm/exynos
branch. Patch 3 doesn't really belong into my tree, please let me know
if there are any objections against it being there and I'll drop it.


	Joerg



  parent reply	other threads:[~2014-05-14 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 20:48 [PATCH v3 0/4] Clean up DMA API docs and dma_addr_t usage Bjorn Helgaas
2014-05-08 20:48 ` [PATCH v3 1/4] DMA-API: Clarify physical/bus address distinction Bjorn Helgaas
2014-05-09  2:49   ` Greg Kroah-Hartman
2014-05-09  6:12   ` Arnd Bergmann
2014-05-09 14:09     ` James Bottomley
2014-05-08 20:49 ` [PATCH v3 2/4] DMA-API: Change dma_declare_coherent_memory() CPU address to phys_addr_t Bjorn Helgaas
2014-05-09  2:50   ` Greg Kroah-Hartman
2014-05-08 20:49 ` [PATCH v3 3/4] sh/PCI: Pass GAPSPCI_DMA_BASE CPU & bus address to dma_declare_coherent_memory() Bjorn Helgaas
2014-05-26 14:46   ` Geert Uytterhoeven
2014-05-26 23:33     ` Bjorn Helgaas
2014-05-08 20:49 ` [PATCH v3 4/4] iommu/exynos: Remove unnecessary "&" from function pointers Bjorn Helgaas
2014-05-14 10:23 ` Joerg Roedel [this message]
2014-05-14 15:50   ` [PATCH v3 0/4] Clean up DMA API docs and dma_addr_t usage Randy Dunlap
2014-05-14 15:56     ` Joerg Roedel

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=20140514102307.GD6026@8bytes.org \
    --to=joro@8bytes.org \
    --cc=Liviu.Dudau@arm.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbottomley@parallels.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).