From: Andi Kleen <ak@suse.de>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: jdmason@us.ibm.com, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH 0 of 7] x86-64: Calgary IOMMU updates
Date: Wed, 26 Jul 2006 00:25:56 +0200 [thread overview]
Message-ID: <200607260025.56903.ak@suse.de> (raw)
In-Reply-To: <patchbomb.1153846590@rhun.haifa.ibm.com>
On Tuesday 25 July 2006 18:56, Muli Ben-Yehuda wrote:
> Hi Andi,
>
> This patchset contains a few Calgary bug fixes (mostly in the error
> handling) and a few harmless associated cleanups (e.g., rearranging
> structures for better alignment). It would be good to get these,
> especially the bug fixes, into 2.6.18.
How do these patches relate to the two earlier patches that Jon sent?
2.6.18 is closed for anything but bug fixes for serious bugs.
-Andi
next prev parent reply other threads:[~2006-07-25 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:56 [PATCH 0 of 7] x86-64: Calgary IOMMU updates Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 1 of 7] [x86-64] Calgary IOMMU: rearrange 'struct iommu_table' members Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 2 of 7] [x86-64] Calgary IOMMU: consolidate per bus data structures Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 3 of 7] [x86-64] Calgary IOMMU: break out of pci_find_device_reverse if dev not found Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 4 of 7] [x86-64] Calgary IOMMU: fix error path memleak in calgary_free_tar Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 5 of 7] [x86-64] Calgary IOMMU: fix reference counting of Calgary PCI devices Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 6 of 7] [x86-64] Calgary IOMMU: calgary_init_one_nontraslated() can return void Muli Ben-Yehuda
2006-07-25 16:56 ` [PATCH 7 of 7] [x86-64] Calgary IOMMU: save a bit of space in bus_info Muli Ben-Yehuda
2006-07-25 22:25 ` Andi Kleen [this message]
2006-07-25 23:07 ` [PATCH 0 of 7] x86-64: Calgary IOMMU updates Jon Mason
2006-07-26 0:06 ` Andi Kleen
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=200607260025.56903.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jdmason@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
/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