From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-omap@vger.kernel.org,
Suman Anna <s-anna@ti.com>
Subject: Re: [GIT PULL FOR v3.16] OMAP IOMMU fixes
Date: Wed, 16 Apr 2014 16:28:05 +0200 [thread overview]
Message-ID: <6806421.DjEURPCCWM@avalon> (raw)
In-Reply-To: <20140416140107.GA3627@8bytes.org>
Hi Joerg,
On Wednesday 16 April 2014 16:01:07 Joerg Roedel wrote:
> Hi Laurent,
>
> On Fri, Apr 04, 2014 at 12:11:52AM +0200, Laurent Pinchart wrote:
> > Laurent Pinchart (3):
> > iommu/omap: Fix 'no page for' debug message in flush_iotlb_page()
> > iommu/omap: Remove comment about supporting single page mappings
> > only
> > iommu/omap: Fix map protection value handling
> >
> > Suman Anna (3):
> > iommu/omap: Correct init value of iotlb_entry valid field
> > iommu/omap: Remove omap_iommu_domain_has_cap() function
> > iommu/omap: Move to_iommu definition from omap-iopgtable.h
> >
> > drivers/iommu/omap-iommu.c | 31 ++++++++++++-------------------
> > drivers/iommu/omap-iopgtable.h | 3 ---
> > 2 files changed, 12 insertions(+), 22 deletions(-)
>
> Can you please rebase this to v3.15-rc1 and send a new pull request? I
> get a lot of commits besides these when I pull into v3.15-rc1.
Sure. The branch was based on top of your iommu master branch, I'll rebase on
top of v3.15-rc1 and resend a pull request.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-16 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 22:11 [GIT PULL FOR v3.16] OMAP IOMMU fixes Laurent Pinchart
2014-04-16 14:01 ` Joerg Roedel
2014-04-16 14:28 ` Laurent Pinchart [this message]
2014-04-16 14:51 ` [GIT PULL v2 " Laurent Pinchart
2014-04-16 14:57 ` Laurent Pinchart
2014-04-16 19:31 ` Joerg Roedel
2014-04-16 23:43 ` Laurent Pinchart
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=6806421.DjEURPCCWM@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-anna@ti.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.