LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeff Garzik <jeff@garzik.org>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
	mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] AMD IOMMU fixes for 2.6.28
Date: Thu, 6 Nov 2008 21:29:07 +0100	[thread overview]
Message-ID: <20081106202907.GC3578@elte.hu> (raw)
In-Reply-To: <49133D15.4020607@garzik.org>


* Jeff Garzik <jeff@garzik.org> wrote:

> Joerg Roedel wrote:
>> Hi Ingo,
>>
>> The following changes since commit 1e19b16a30c34c042f1eaa23db4c99bfad1dac0e:
>>   Thomas Gleixner (1):
>>         AMD IOMMU: use iommu_device_max_index, fix
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git iommu-fixes-2.6.28
>>
>> Joerg Roedel (2):
>>       AMD IOMMU: fix detection of NP capable IOMMUs
>>       AMD IOMMU: fix lazy IO/TLB flushing in unmap path
>>
>>  arch/x86/kernel/amd_iommu.c |    9 +++++++--
>>  1 files changed, 7 insertions(+), 2 deletions(-)
>>
>> This are 2 important bugfixes which fix lazy IO/TLB flushing with the
>> driver. Please pull.
>
> Even though the x86 maintainers probably don't require it, it would 
> be nice if you could include the changes being pushed in the same 
> email (provided the patch is under 400k).  Every little bit of 
> additional review helps.

agreed, that would be nice to have for future pull requests.

	Ingo

      reply	other threads:[~2008-11-06 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 14:15 [GIT PULL] AMD IOMMU fixes for 2.6.28 Joerg Roedel
2008-11-06 14:24 ` Ingo Molnar
2008-11-06 18:53 ` Jeff Garzik
2008-11-06 20:29   ` 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=20081106202907.GC3578@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).