[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090111132204L.fujita.tomonori@lab.ntt.co.jp>
Date: Sun, 11 Jan 2009 13:22:10 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: mingo@...e.hu
Cc: fujita.tomonori@....ntt.co.jp, Ian.Campbell@...rix.com,
linux-kernel@...r.kernel.org, jeremy@...p.org, jj@...osbits.net,
weiyi.huang@...il.com, beckyb@...nel.crashing.org
Subject: Re: [PATCH 0/2] Re: swiotlb: remove duplicated #include
On Sun, 11 Jan 2009 05:04:28 +0100
Ingo Molnar <mingo@...e.hu> wrote:
>
> * FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:
>
> > On Sun, 11 Jan 2009 04:55:27 +0100
> > Ingo Molnar <mingo@...e.hu> wrote:
> >
> > >
> > > * Ian Campbell <Ian.Campbell@...rix.com> wrote:
> > >
> > > > On Fri, 2009-01-09 at 18:10 +0000, Ian Campbell wrote:
> > > >
> > > > > Patch is against Jeremy's Xen patch queue which is based on a pre-Xmas
> > > > > tip tree so fairly out of date, I hope it is somewhat useful though.
> > > >
> > > > Here's a version again tip-latest, only compile tested though since my
> > > > testing relies on the Xen dom0 patch queue.
> > >
> > > Applied them to tip/core/iommu:
> > >
> > > 961d7d0: swiotlb: do not use sg_virt()
> > > 0b8698a: swiotlb: range_needs_mapping should take a physical address.
> >
> > I think that Xen camp wants these changes for 2.6.29. Are you trying to
> > push tip/core/iommu for 2.6.29?
>
> Yet unclear, depends on testing. Will probably wait for 2.6.30 though.
Thanks, I see. Probably, it will get tons of conflict due to the dma
API unification touching everywhere.
BTW, what happened to?
http://marc.info/?l=linux-kernel&m=123125853906986&w=2
It's better to have these (especially Becky's work) in mainline now.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists