From: Joerg Roedel <joro@8bytes.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: alex.williamson@redhat.com, Varun.Sethi@freescale.com,
aik@ozlabs.ru, joe@perches.com, rostedt@goodmis.org,
fweisbec@gmail.com, mingo@redhat.com, tony@atomide.com,
ohad@wizery.com, andreas.herrmann@calxeda.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, shuahkhan@gmail.com
Subject: Re: [PATCH 0/7] iommu: Add event tracing feature to iommu
Date: Tue, 24 Sep 2013 12:38:17 +0200 [thread overview]
Message-ID: <20130924103816.GA4532@8bytes.org> (raw)
In-Reply-To: <cover.1376587770.git.shuah.kh@samsung.com>
On Thu, Aug 15, 2013 at 11:59:22AM -0600, Shuah Khan wrote:
> Shuah Khan (7):
> iommu: Add event tracing feature to iommu
> iommu: Change iommu driver to call add_device_to_group trace event
> iommu: Change iommu driver to call remove_device_to_group trace event
> iommu: Change iommu driver to call attach_device_to_domain trace
> event
> iommu: Change iommu driver to call detach_device_to_domain trace
> event
> iommu: Change iommu driver to call map trace event
> iommu: Change iommu driver to call unmap trace event
Applied to tracing branch, thanks Shuah.
prev parent reply other threads:[~2013-09-24 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 17:59 [PATCH 0/7] iommu: Add event tracing feature to iommu Shuah Khan
2013-08-15 17:59 ` [PATCH 1/7] " Shuah Khan
2013-08-15 17:59 ` [PATCH 2/7] iommu: Change iommu driver to call add_device_to_group trace event Shuah Khan
2013-08-15 17:59 ` [PATCH 3/7] iommu: Change iommu driver to call remove_device_to_group " Shuah Khan
2013-08-15 17:59 ` [PATCH 4/7] iommu: Change iommu driver to call attach_device_to_domain " Shuah Khan
2013-08-15 17:59 ` [PATCH 5/7] iommu: Change iommu driver to call detach_device_to_domain " Shuah Khan
2013-08-15 17:59 ` [PATCH 6/7] iommu: Change iommu driver to call map " Shuah Khan
2013-08-15 17:59 ` [PATCH 7/7] iommu: Change iommu driver to call unmap " Shuah Khan
2013-09-24 10:38 ` 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=20130924103816.GA4532@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=andreas.herrmann@calxeda.com \
--cc=fweisbec@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ohad@wizery.com \
--cc=rostedt@goodmis.org \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@gmail.com \
--cc=tony@atomide.com \
--cc=will.deacon@arm.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 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).