From: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [GIT PULL v2 FOR v3.16] OMAP IOMMU fixes
Date: Wed, 16 Apr 2014 16:51:56 +0200 [thread overview]
Message-ID: <1527771.aIpQeXENtj@avalon> (raw)
In-Reply-To: <6806421.DjEURPCCWM@avalon>
Hi Joerg,
The following changes since commit c9eaa447e77efe77b7fa4c953bd62de8297fd6c5:
Linux 3.15-rc1 (2014-04-13 14:18:35 -0700)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git iommu/omap
for you to fetch changes up to 286f600bc890347f7ec7bd50d33210d53a9095a3:
iommu/omap: Fix map protection value handling (2014-04-16 16:30:18 +0200)
Compared to the v1 pull request, the patches have been rebased directly on top
of v3.15-rc1.
----------------------------------------------------------------
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 prev parent reply other threads:[~2014-04-16 14:51 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
2014-04-16 14:51 ` Laurent Pinchart [this message]
2014-04-16 14:57 ` [GIT PULL v2 " 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=1527771.aIpQeXENtj@avalon \
--to=laurent.pinchart-rylnwiuwjnjg/c1bvhzhaw@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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