From: Ingo Molnar <mingo@elte.hu>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] amd iommu fixes for 2.6.35-rc1
Date: Tue, 1 Jun 2010 11:45:58 +0200 [thread overview]
Message-ID: <20100601094558.GA22265@elte.hu> (raw)
In-Reply-To: <1275383021-20172-1-git-send-email-joerg.roedel@amd.com>
* Joerg Roedel <joerg.roedel@amd.com> wrote:
> Hi Ingo,
>
> The following changes since commit 67a3e12b05e055c0415c556a315a3d3eb637e29e:
>
> Linux 2.6.35-rc1 (2010-05-30 13:21:02 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git amd-iommu/2.6.35
>
> Joerg Roedel (3):
> Merge commit 'v2.6.35-rc1' into amd-iommu/2.6.35
> x86/amd-iommu: Fix crash when request_mem_region fails
> x86/amd-iommu: Fall back to GART if initialization fails
>
> Julia Lawall (1):
> arch/x86/kernel: Add missing spin_unlock
>
> arch/x86/kernel/amd_iommu.c | 16 +++++++++-------
> arch/x86/kernel/amd_iommu_init.c | 20 +++++++++++++++++---
> 2 files changed, 26 insertions(+), 10 deletions(-)
>
> These patches fix two bugs in the error-paths of the amd iommu driver. One
> fix adds missing spin_unlocks and the other two patches fix a problem with
> broken BIOSes where the driver can't allocate the mmio region for the iommu
> hardware. Please pull.
Pulled, thanks Joerg!
Ingo
prev parent reply other threads:[~2010-06-01 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 9:03 [git pull] amd iommu fixes for 2.6.35-rc1 Joerg Roedel
2010-06-01 9:03 ` [PATCH 1/3] arch/x86/kernel: Add missing spin_unlock Joerg Roedel
2010-06-01 9:03 ` [PATCH 2/3] x86/amd-iommu: Fix crash when request_mem_region fails Joerg Roedel
2010-06-01 9:03 ` [PATCH 3/3] x86/amd-iommu: Fall back to GART if initialization fails Joerg Roedel
2010-06-01 9:45 ` 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=20100601094558.GA22265@elte.hu \
--to=mingo@elte.hu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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