public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] amd-iommu: kdump bugfix and couple defensive cleanups
Date: Mon, 15 Jun 2009 11:48:48 +0200	[thread overview]
Message-ID: <20090615094848.GD5139@amd.com> (raw)
In-Reply-To: <20090612030341.GQ20823@sequoia.sous-sol.org>

On Thu, Jun 11, 2009 at 08:03:41PM -0700, Chris Wright wrote:
> The following patches fix a kdump issue and then fix some similar
> initialization issues that haven't proven to be problematic but make
> good sense anyway.

The patches look good but are based on 2.6.30. For 2.6.31-rc1 they must
be changed a bit because some functions implemented in these patches
were already merged for the suspen/resume support in amd-iommu driver.
I will adapt them for 2.6.31. Do you want to send these patches for
-stable inclusion?

	Joerg

-- 
           | Advanced Micro Devices GmbH
 Operating | Karl-Hammerschmidt-Str. 34, 85609 Dornach bei München
 System    | 
 Research  | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
 Center    | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
           | Registergericht München, HRB Nr. 43632


  parent reply	other threads:[~2009-06-15  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  3:03 [PATCH 0/2] amd-iommu: kdump bugfix and couple defensive cleanups Chris Wright
2009-06-12  3:04 ` [PATCH 1/2] amd-iommu: fix issues with kdump Chris Wright
2009-06-12  3:05 ` [PATCH 2/2] amd-iommu: initialization fixes Chris Wright
2009-06-15  9:48 ` Joerg Roedel [this message]
2009-06-15 16:33   ` [PATCH 0/2] amd-iommu: kdump bugfix and couple defensive cleanups Chris Wright

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=20090615094848.GD5139@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=chrisw@sous-sol.org \
    --cc=iommu@lists.linux-foundation.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