From: Joerg Roedel <joro@8bytes.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
fenghua.yu@intel.com, tony.luck@intel.com,
suresh.b.siddha@intel.com, sfr@canb.auug.org.au,
andreas.herrmann3@amd.com, joseph.cihula@intel.com,
akpm@linux-foundation.org, jbarnes@virtuousgeek.org,
tglx@linutronix.de, torvalds@linux-foundation.org, mingo@elte.hu
Subject: Re: [ANNOUNCE] iommu-2.6.git tree
Date: Sun, 19 Oct 2008 13:12:03 +0200 [thread overview]
Message-ID: <20081019111203.GB29705@8bytes.org> (raw)
In-Reply-To: <1224343843.6770.1378.camel@macbook.infradead.org>
On Sat, Oct 18, 2008 at 04:30:43PM +0100, David Woodhouse wrote:
> 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
Is there a specific reason why IOMMU stuff should go to Linus without
testing them in the x86 tree before? The DMA layer and IOMMU drivers are
an integral component of the architecture and patches for it are best
placed in the architecture tree instead of a seperate one, imho.
Joerg
next prev parent reply other threads:[~2008-10-19 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 15:30 [ANNOUNCE] iommu-2.6.git tree David Woodhouse
2008-10-18 15:43 ` Stephen Rothwell
2008-10-18 15:51 ` David Woodhouse
2008-10-19 11:12 ` Joerg Roedel [this message]
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=20081019111203.GB29705@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.herrmann3@amd.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--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