From: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Subject: Re: [GIT PULL] iommu/arm-smmu: ARM SMMUv3 fixes for 4.2
Date: Fri, 10 Jul 2015 17:41:02 +0200 [thread overview]
Message-ID: <20150710154102.GJ2566@suse.de> (raw)
In-Reply-To: <20150710135742.GA3341-5wv7dgnIgG8@public.gmane.org>
On Fri, Jul 10, 2015 at 02:57:42PM +0100, Will Deacon wrote:
> Please can you pull these ARM SMMUv3 fixes for 4.2?
> Thunder has done a good job of turning these around and they fix real
> issues that he's seeing on his platform.
Pulled to iommu/fixes.
WARNING: multiple messages have this Message-ID (diff)
From: jroedel@suse.de (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu/arm-smmu: ARM SMMUv3 fixes for 4.2
Date: Fri, 10 Jul 2015 17:41:02 +0200 [thread overview]
Message-ID: <20150710154102.GJ2566@suse.de> (raw)
In-Reply-To: <20150710135742.GA3341@arm.com>
On Fri, Jul 10, 2015 at 02:57:42PM +0100, Will Deacon wrote:
> Please can you pull these ARM SMMUv3 fixes for 4.2?
> Thunder has done a good job of turning these around and they fix real
> issues that he's seeing on his platform.
Pulled to iommu/fixes.
next prev parent reply other threads:[~2015-07-10 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 13:57 [GIT PULL] iommu/arm-smmu: ARM SMMUv3 fixes for 4.2 Will Deacon
2015-07-10 13:57 ` Will Deacon
[not found] ` <20150710135742.GA3341-5wv7dgnIgG8@public.gmane.org>
2015-07-10 15:41 ` Joerg Roedel [this message]
2015-07-10 15:41 ` 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=20150710154102.GJ2566@suse.de \
--to=jroedel-l3a5bk7wagm@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@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 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.