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: [GIT PULL FOR v3.16] OMAP IOMMU fixes
Date: Fri, 04 Apr 2014 00:11:52 +0200 [thread overview]
Message-ID: <2312051.xNuD1CfeZH@avalon> (raw)
Hi Joerg,
The following changes since commit 8944b7d495a00ae44d19ce945b5032a86dcdf7f0:
Merge branch 'next' (2014-03-04 23:41:51 +0100)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git iommu/omap
for you to fetch changes up to f42ed2dcc15e39a189458cfab69d7f2b902cc3e6:
iommu/omap: Fix map protection value handling (2014-04-03 23:35:39 +0200)
I will need to base an OMAP3 ISP patch set on top of this, and I would like to
get it merged in v3.16 as well. In order to avoid bisection breakages, could
you merge this right on top of v3.15-rc1 when it will be out and provide a
stable branch that can then be merged in the Linux media tree ?
----------------------------------------------------------------
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(-)
--
Regards,
Laurent Pinchart
next reply other threads:[~2014-04-03 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 22:11 Laurent Pinchart [this message]
2014-04-16 14:01 ` [GIT PULL FOR v3.16] OMAP IOMMU fixes Joerg Roedel
2014-04-16 14:28 ` Laurent Pinchart
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=2312051.xNuD1CfeZH@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox