From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Tue, 20 Jun 2017 09:10:45 +0000 Subject: Re: [PATCH 03/11] au1100fb: remove a bogus dma_free_nonconsistent call Message-Id: <20170620091045.GA10272@lst.de> List-Id: References: <20170616071716.17321-1-hch@lst.de> <20170616071716.17321-4-hch@lst.de> <8727942.IUH8e0tH8t@amdc3058> In-Reply-To: <8727942.IUH8e0tH8t@amdc3058> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Bartlomiej Zolnierkiewicz Cc: linux-fbdev@vger.kernel.org, linux-scsi@vger.kernel.org, netdev@vger.kernel.org, alsa-devel@alsa-project.org, Christoph Hellwig , linux-serial@vger.kernel.org, nios2-dev@lists.rocketboards.org, linux-metag@vger.kernel.org, linux-kernel@vger.kernel.org On Mon, Jun 19, 2017 at 01:15:04PM +0200, Bartlomiej Zolnierkiewicz wrote: > On Friday, June 16, 2017 09:17:08 AM Christoph Hellwig wrote: > > au1100fb is using managed dma allocations, so it doesn't need to > > explicitly free the dma memory in the error path (and if it did > > it would have to use the managed version). > > > > Signed-off-by: Christoph Hellwig > > Acked-by: Bartlomiej Zolnierkiewicz Are you fine with picking this up through the new dma-mapping tree?