From: Ingo Molnar <mingo@elte.hu>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull][PATCH 0/4] amd-iommu fixes for tip/core/iommu
Date: Tue, 9 Jun 2009 16:21:10 +0200 [thread overview]
Message-ID: <20090609142110.GB32703@elte.hu> (raw)
In-Reply-To: <1244555840-3855-1-git-send-email-joerg.roedel@amd.com>
* Joerg Roedel <joerg.roedel@amd.com> wrote:
> Hi Ingo,
>
> The following changes since commit 62a6f465f6572e1f28765c583c12753bb3e23715:
> Ingo Molnar (1):
> Merge branch 'dma-debug/2.6.31' of git://git.kernel.org/.../joro/linux-2.6-iommu into core/iommu
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git amd-iommu/fixes
>
> Jiri Slaby (1):
> amd_iommu: fix lock imbalance
>
> Joerg Roedel (4):
> Merge commit 'tip/core/iommu' into amd-iommu/fixes
> amd-iommu: remove BUS_NOTIFY_BOUND_DRIVER handling
> amd-iommu: detach device explicitly before attaching it to a new domain
> amd-iommu: remove unnecessary "AMD IOMMU: " prefix
>
> arch/x86/kernel/amd_iommu.c | 22 ++++++----------------
> 1 files changed, 6 insertions(+), 16 deletions(-)
>
> These patches fix issues with device assignment to KVM, a possible
> deadlock due to an unreleased lock and a minor printk style issue.
> Please pull.
Pulled into tip:core/iommu, thanks a lot Joerg!
Ingo
prev parent reply other threads:[~2009-06-09 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 13:57 Joerg Roedel
2009-06-09 13:57 ` [PATCH 1/4] amd_iommu: fix lock imbalance Joerg Roedel
2009-06-09 13:57 ` [PATCH 2/4] amd-iommu: remove BUS_NOTIFY_BOUND_DRIVER handling Joerg Roedel
2009-06-09 14:15 ` Chris Wright
2009-06-09 13:57 ` [PATCH 3/4] amd-iommu: detach device explicitly before attaching it to a new domain Joerg Roedel
2009-06-09 13:57 ` [PATCH 4/4] amd-iommu: remove unnecessary "AMD IOMMU: " prefix Joerg Roedel
2009-06-09 14:21 ` Ingo Molnar [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=20090609142110.GB32703@elte.hu \
--to=mingo@elte.hu \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--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
all inboxes | Powered by JetHome®