From: David Woodhouse <dwmw2@infradead.org>
To: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: joerg.roedel@amd.com, tglx@linutronix.de, mingo@elte.hu,
fujita.tomonori@lab.ntt.co.jp, andreas.herrmann3@amd.com,
joseph.cihula@intel.com, fenghua.yu@intel.com,
jbarnes@virtuousgeek.org, tony.luck@intel.com,
suresh.b.siddha@intel.com, sfr@canb.auug.org.au,
torvalds@linux-foundation.org, akpm@linux-foundation.org
Subject: [ANNOUNCE] iommu-2.6.git tree
Date: Sat, 18 Oct 2008 16:30:43 +0100 [thread overview]
Message-ID: <1224343843.6770.1378.camel@macbook.infradead.org> (raw)
As previously threatened, I've created an iommu-2.6.git tree:
git://git.infradead.org/iommu-2.6.git
http://git.infradead.org/iommu-2.6.git
I've rounded up the patches which have been pending for a while and
which would have been in linux-next if Stephen hadn't been away, and I'm
planning to ask Linus to pull it early next week, before the merge
window closes.
If there's anything missing which should be in 2.6.28, now is the time
to shout. I don't want anything new and exciting yet though please; only
patches which have already been posted and reviewed, or necessary fixes.
Stephen, please could you add this tree to linux-next?
Current contents:
Andreas Herrmann (1):
amd_iommu: fix nasty bug that caused ILLEGAL_DEVICE_TABLE_ENTRY errors
Cihula, Joseph (1):
intel-iommu: disable Protected Memory Regions when DMA remapping enabled
David Woodhouse (2):
dmar: fix uninitialised 'ret' variable in dmar_parse_dev()
Admit to maintaining VT-d, for my sins.
FUJITA Tomonori (1):
intel-iommu: use coherent_dma_mask in alloc_coherent
Fenghua Yu (1):
intel-iommu: IA64 support
Suresh Siddha (1):
dmar: use spin_lock_irqsave() in qi_submit_sync()
Youquan Song (3):
dmar: context cache and IOTLB invalidation using queued invalidation
dmar: Use queued invalidation interface for IOTLB and context invalidation
dmar: remove the quirk which disables dma-remapping when intr-remapping enabled
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next reply other threads:[~2008-10-18 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 15:30 David Woodhouse [this message]
2008-10-18 15:43 ` Stephen Rothwell
2008-10-18 15:51 ` David Woodhouse
2008-10-19 11:12 ` Joerg Roedel
2008-10-19 11:19 ` David Woodhouse
2008-10-19 12:47 ` Ingo Molnar
2008-10-19 13:21 ` David Woodhouse
2008-10-19 17:26 ` Ingo Molnar
2008-10-19 17:42 ` David Woodhouse
2008-10-19 21:21 ` Peter Zijlstra
2008-10-19 21:22 ` Joerg Roedel
2008-10-20 16:41 ` Luck, Tony
2008-10-19 21:23 ` Joerg Roedel
2008-10-20 3:32 ` FUJITA Tomonori
2008-10-20 18:06 ` Yu, Fenghua
2008-10-20 23:51 ` FUJITA Tomonori
2008-10-19 21:14 ` Joerg Roedel
2008-10-20 7:43 ` David Woodhouse
2008-10-20 8:52 ` Ingo Molnar
2008-10-20 9:07 ` David Woodhouse
2008-10-20 0:46 ` FUJITA Tomonori
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=1224343843.6770.1378.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.herrmann3@amd.com \
--cc=fenghua.yu@intel.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=joerg.roedel@amd.com \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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®