Re: [PATCH v2] media: atomisp: Fix error handling path

2020-11-03 Thread Markus Elfring
> Fixes: 14a638ab96c5 ("media: atomisp: use pin_user_pages() for memory > allocation") Please delete a line break for this tag. Regards, Markus ___ devel mailing list de...@linuxdriverproject.org

RE: [PATCH v6 2/8] clk: clock-wizard: Add the clockwizard to clk directory

2020-11-03 Thread Shubhrajyoti Datta
Hi Stephen, Thanks for the review. > -Original Message- > From: Stephen Boyd > Sent: Tuesday, September 22, 2020 2:52 AM > To: Shubhrajyoti Datta ; linux-...@vger.kernel.org > Cc: devicet...@vger.kernel.org; linux-ker...@vger.kernel.org; > de...@driverdev.osuosl.org; robh...@kernel.org;

[PATCH v2] media: atomisp: Fixed error handling path

2020-11-03 Thread Souptick Joarder
Inside alloc_user_pages() based on flag value either pin_user_pages() or get_user_pages_fast() will be called. However, these API might fail. But free_user_pages() called in error handling path doesn't bother about return value and will try to unpin bo->pgnr pages, which is incorrect. Fix this

use of dma_direct_set_offset in (allwinner) drivers

2020-11-03 Thread Christoph Hellwig
Hi all, Linux 5.10-rc1 switched from having a single dma offset in struct device to a set of DMA ranges, and introduced a new helper to set them, dma_direct_set_offset. This in fact surfaced that a bunch of drivers that violate our layering and set the offset from drivers, which meant we had to