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 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges
Date: Wed, 3 May 2017 10:37:32 +0530 [thread overview]
Message-ID: <CAMSpPPd13jZWr+sThEpD8sqgoVJ5O5azTe0sGixzVNx3ADT0Mg@mail.gmail.com> (raw)
In-Reply-To: <1493786795-28153-3-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
next prev parent reply other threads:[~2017-05-03 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1493786795-28153-1-git-send-email-oza.oza@broadcom.com>
2017-05-03 19:55 ` [PATCH 1/3] of/pci/dma: fix DMA configuration for PCI masters Rob Herring
[not found] ` <1493786795-28153-3-git-send-email-oza.oza@broadcom.com>
2017-05-03 5:07 ` Oza Oza [this message]
2017-05-03 20:06 ` [PATCH 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges Rob Herring
2017-05-04 18:02 ` [PATCH 1/3] of/pci/dma: fix DMA configuration for PCI masters Robin Murphy
[not found] ` <CAMSpPPcC6wN+2HeZPak+gWxoy2WaO14epHNQfHT1W0FnTRHnOQ@mail.gmail.com>
2017-05-05 15:25 ` Robin Murphy
[not found] ` <1493786795-28153-2-git-send-email-oza.oza@broadcom.com>
2017-05-04 18:20 ` [PATCH 2/3] iommu/pci: reserve iova " Robin Murphy
[not found] ` <CAMSpPPdtfMMkTpi9cWn0QV2qnfBoHayQQg5cGANAswSwFoHX3w@mail.gmail.com>
2017-05-05 15:51 ` 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=CAMSpPPd13jZWr+sThEpD8sqgoVJ5O5azTe0sGixzVNx3ADT0Mg@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).