From: Joerg Roedel <joro@8bytes.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
iommu@lists.linux-foundation.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Don't truncate ttbr if LPAE is not enabled
Date: Mon, 28 Dec 2015 17:12:03 +0100 [thread overview]
Message-ID: <20151228161203.GC17673@8bytes.org> (raw)
In-Reply-To: <1450810866-4716-1-git-send-email-geert+renesas@glider.be>
On Tue, Dec 22, 2015 at 08:01:06PM +0100, Geert Uytterhoeven wrote:
> static int ipmmu_domain_init_context(struct ipmmu_vmsa_domain *domain)
> {
> - phys_addr_t ttbr;
> + u64 ttbr;
> u32 tmp;
> int ret;
Didn't apply cleanly to v4.4-rc7, but fixed it up and queued it to
iommu/fixes.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
iommu@lists.linux-foundation.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Don't truncate ttbr if LPAE is not enabled
Date: Mon, 28 Dec 2015 16:12:03 +0000 [thread overview]
Message-ID: <20151228161203.GC17673@8bytes.org> (raw)
In-Reply-To: <1450810866-4716-1-git-send-email-geert+renesas@glider.be>
On Tue, Dec 22, 2015 at 08:01:06PM +0100, Geert Uytterhoeven wrote:
> static int ipmmu_domain_init_context(struct ipmmu_vmsa_domain *domain)
> {
> - phys_addr_t ttbr;
> + u64 ttbr;
> u32 tmp;
> int ret;
Didn't apply cleanly to v4.4-rc7, but fixed it up and queued it to
iommu/fixes.
next prev parent reply other threads:[~2015-12-28 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 19:01 [PATCH] iommu/ipmmu-vmsa: Don't truncate ttbr if LPAE is not enabled Geert Uytterhoeven
2015-12-22 19:01 ` Geert Uytterhoeven
2015-12-28 16:12 ` Joerg Roedel [this message]
2015-12-28 16:12 ` Joerg Roedel
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=20151228161203.GC17673@8bytes.org \
--to=joro@8bytes.org \
--cc=geert+renesas@glider.be \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.