[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100826185102I.fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 26 Aug 2010 18:51:48 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: g.liakhovetski@....de
Cc: fujita.tomonori@....ntt.co.jp, mitov@...p.bas.bg,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
akpm@...ux-foundation.org, linux-arm-kernel@...ts.infradead.org,
linux-sh@...r.kernel.org, u.kleine-koenig@...gutronix.de,
philippe.retornaz@...l.ch, gregkh@...e.de, jkrzyszt@....icnet.pl
Subject: Re: [RFC][PATCH] add
dma_reserve_coherent_memory()/dma_free_reserved_memory() API
On Thu, 26 Aug 2010 11:45:58 +0200 (CEST)
Guennadi Liakhovetski <g.liakhovetski@....de> wrote:
> On Thu, 26 Aug 2010, FUJITA Tomonori wrote:
>
> > Why can't you revert a commit that causes the regression?
>
> See this reply, and the complete thread too.
>
> http://marc.info/?l=linux-sh&m=128130485208262&w=2
>
> > The related DMA API wasn't changed in 2.6.36-rc1. The DMA API is not
> > responsible for the regression. And the patchset even exnteds the
> > definition of the DMA API (dma_declare_coherent_memory). Such change
> > shouldn't applied after rc1. I think that DMA-API.txt says that
> > dma_declare_coherent_memory() handles coherent memory for a particular
> > device. It's not for the API that reserves coherent memory that can be
> > used for any device for a single device.
>
> Anyway, we need a way to fix the regression.
Needs to find a different way.
--
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