From: Takao Indoh <indou.takao@jp.fujitsu.com>
To: bhe@redhat.com
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
dwmw2@infradead.org, joro@8bytes.org, alex.williamson@redhat.com,
kexec@lists.infradead.org
Subject: Re: [PATCH] intel-iommu: Quiesce devices before disabling IOMMU
Date: Mon, 09 Sep 2013 13:46:17 +0900 [thread overview]
Message-ID: <522D5299.9020809@jp.fujitsu.com> (raw)
In-Reply-To: <522D4E8A.8010507@jp.fujitsu.com>
(2013/09/09 13:28), Takao Indoh wrote:
>> BTW, what's the status of Alex's PCI patchset which this patch depends
>> on?
>
> It is merged to Bjorn's tree, will be in v3.12.
This was wrong. Alex's patchset is already in Linus tree, v3.11.
Thanks,
Takao Indoh
next prev parent reply other threads:[~2013-09-09 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 7:15 [PATCH] intel-iommu: Quiesce devices before disabling IOMMU Takao Indoh
2013-09-08 11:47 ` Baoquan He
2013-09-09 4:28 ` Takao Indoh
2013-09-09 4:46 ` Takao Indoh [this message]
2013-09-09 9:07 ` David Woodhouse
2013-09-10 5:43 ` Takao Indoh
2013-09-18 11:29 ` David Woodhouse
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=522D5299.9020809@jp.fujitsu.com \
--to=indou.takao@jp.fujitsu.com \
--cc=alex.williamson@redhat.com \
--cc=bhe@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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