From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu/arm-smmu: updates for 4.1
Date: Tue, 31 Mar 2015 15:40:12 +0200 [thread overview]
Message-ID: <20150331134012.GC22683@8bytes.org> (raw)
In-Reply-To: <20150327172146.GM1562@arm.com>
On Fri, Mar 27, 2015 at 05:21:46PM +0000, Will Deacon wrote:
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git for-joerg/arm-smmu/updates
Pulled, but ...
> Robin Murphy (1):
> iommu/arm-smmu: set a more appropriate DMA mask
>
> Will Deacon (3):
> iommu/arm-smmu: ensure CBA2R is initialised before CBAR on SMMUv2
> iommu/arm-smmu: handle multi-alias IOMMU groups for PCI devices
> iommu/io-pgtable-arm: avoid speculative walks through TTBR1
... next time please make sure the commit subjects start with capital
letters after the colon.
Thanks,
Joerg
prev parent reply other threads:[~2015-03-31 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:21 [GIT PULL] iommu/arm-smmu: updates for 4.1 Will Deacon
2015-03-31 13:40 ` Joerg Roedel [this message]
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=20150331134012.GC22683@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).