[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <201211301157.38802.b.zolnierkie@samsung.com>
Date: Fri, 30 Nov 2012 11:57:38 +0100
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To: Dan Williams <djbw@...com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>,
HÃ¥vard Skinnemoen <hskinnemoen@...il.com>,
Ira Snyder <iws@...o.caltech.edu>,
"Koul, Vinod" <vinod.koul@...el.com>, vipin.kumar@...com,
t.figa@...sung.com,
"kyungmin.park@...sung.com" <kyungmin.park@...sung.com>,
Dave Jiang <dave.jiang@...il.com>
Subject: Re: [PATCH 00/20] DMA: DMA unmap fixes
On Wednesday 07 November 2012 21:40:57 Dan Williams wrote:
> On Mon, Nov 5, 2012 at 2:00 AM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@...sung.com> wrote:
> > Hi,
> >
> > Currently DMA subsystem does DMA mapping in the core code and DMA
> > unmapping is done by device drivers. This is counterintuitive,
> > causes code duplication and subtle errors (some drivers like PL330
> > one don't implement DMA unmapping code). The following patchset
> > modifies DMA subsystem to do DMA unmapping in the core code.
> > It results in simpler code, less code duplication (more than 400
> > LOC is gone) and fixes the issue with missing DMA unmapping code
> > in some drivers. Additionally many cases when DMA wasn't unmapped
> > on a failure are also fixed.
> >
> >
> > patches #1-3 add missing DMA unmap on failure to async_tx core
> > code (async_memcpy()), ioat and fsmc_nand drivers
> >
> > patch #4 fixes DMA flags used by carma-fpga driver
>
> Ack patches 1-4
[...]
> > patch #8 adds missing DMA unmap on failure to ioat3 driver
> >
> > patch #9 fixes build for async_memset.c
> >
> > patch #10 adds missing DMA unmap on failure to async tx core
> > code (async_memset())
>
> Ack patches 8-10
Thank you.
Could these patches be merged for 3.8 by either your's or Vinod's tree?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung Poland R&D Center
--
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