linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oza Oza <oza.oza@broadcom.com>
To: Joerg Roedel <joro@8bytes.org>, Robin Murphy <robin.murphy@arm.com>
Cc: Linux IOMMU <iommu@lists.linux-foundation.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
	Oza Pawandeep <oza.pawandeep@gmail.com>,
	Oza Pawandeep <oza.oza@broadcom.com>
Subject: Re: [PATCH 1/3] of/pci/dma: fix DMA configuration for PCI masters
Date: Wed, 3 May 2017 10:36:10 +0530	[thread overview]
Message-ID: <CAMSpPPdYJE80nAGS7O5tG5YWprWi3wts5ZjJXhfgpG3kY5Kbvw@mail.gmail.com> (raw)
In-Reply-To: <1493786795-28153-1-git-send-email-oza.oza@broadcom.com>

I will send v2 after removing GERRIT details from
commit message. My apologies for the noise.

Regards,
Oza

  parent reply	other threads:[~2017-05-03  5:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  4:46 [PATCH 1/3] of/pci/dma: fix DMA configuration for PCI masters Oza Pawandeep
2017-05-03  4:46 ` [PATCH 2/3] iommu/pci: reserve iova " Oza Pawandeep
2017-05-03  5:07   ` Oza Oza
2017-05-04 18:20   ` Robin Murphy
2017-05-04 18:52     ` Oza Oza
2017-05-05 15:51       ` Robin Murphy
2017-05-06  6:01         ` Oza Oza
2017-05-22 16:45         ` Oza Oza
2017-05-05  8:10     ` Oza Oza
2017-05-03  4:46 ` [PATCH 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges Oza Pawandeep
2017-05-03  5:07   ` Oza Oza
2017-05-03 20:06   ` Rob Herring
2017-05-03  5:06 ` Oza Oza [this message]
2017-05-03 19:55 ` [PATCH 1/3] of/pci/dma: fix DMA configuration for PCI masters Rob Herring
2017-05-04 18:02 ` Robin Murphy
2017-05-04 18:41   ` Oza Oza
2017-05-05 15:25     ` Robin Murphy
2017-05-06  5:30       ` Oza Oza
2017-05-16  5:24         ` Oza Oza
2017-05-04 19:12   ` Oza Oza

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=CAMSpPPdYJE80nAGS7O5tG5YWprWi3wts5ZjJXhfgpG3kY5Kbvw@mail.gmail.com \
    --to=oza.oza@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=oza.pawandeep@gmail.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 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).