From: Joerg Roedel <joro@8bytes.org>
To: Will Deacon <will.deacon@arm.com>
Cc: robin.murphy@arm.com, yong.wu@mediatek.com,
laurent.pinchart@ideasonboard.com,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH] iommu/io-pgtable-arm: Unmap and free table when overwriting with block
Date: Tue, 18 Aug 2015 11:28:40 +0200 [thread overview]
Message-ID: <20150818092840.GA26556@8bytes.org> (raw)
In-Reply-To: <1439308112-29758-1-git-send-email-will.deacon@arm.com>
On Tue, Aug 11, 2015 at 04:48:32PM +0100, Will Deacon wrote:
> Joerg, could you queue this up for 4.3 please? It's a fix, but it's late
> in the day for 4.2 and doesn't backport cleanly. Merging it with the Cc
> stable tag is probably the easiest thing to do, then I can fix up the
> conflicts as they arise.
Applied, thanks Will.
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/io-pgtable-arm: Unmap and free table when overwriting with block
Date: Tue, 18 Aug 2015 11:28:40 +0200 [thread overview]
Message-ID: <20150818092840.GA26556@8bytes.org> (raw)
In-Reply-To: <1439308112-29758-1-git-send-email-will.deacon@arm.com>
On Tue, Aug 11, 2015 at 04:48:32PM +0100, Will Deacon wrote:
> Joerg, could you queue this up for 4.3 please? It's a fix, but it's late
> in the day for 4.2 and doesn't backport cleanly. Merging it with the Cc
> stable tag is probably the easiest thing to do, then I can fix up the
> conflicts as they arise.
Applied, thanks Will.
next prev parent reply other threads:[~2015-08-18 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 15:48 [PATCH] iommu/io-pgtable-arm: Unmap and free table when overwriting with block Will Deacon
2015-08-11 15:48 ` Will Deacon
2015-08-11 15:48 ` Will Deacon
2015-08-18 9:28 ` Joerg Roedel [this message]
2015-08-18 9:28 ` 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=20150818092840.GA26556@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=yong.wu@mediatek.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.