Re: [PATCH v2 1/9] mm: Introduce new vm_insert_range API

2018-12-02 Thread Mike Rapoport
On Mon, Dec 03, 2018 at 09:51:45AM +0530, Souptick Joarder wrote: > Hi Mike, > > On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote: > > > > On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote: > > > Previouly drivers have their own way of mapping range of > > > kernel pages/memory i

cron job: media_tree daily build: OK

2018-12-02 Thread Hans Verkuil
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Mon Dec 3 05:00:11 CET 2018 media-tree git hash:708d75fe1c7c6e9abc5381b6fcc32b49830383d0 media_build git

Re: [PATCH v2 1/9] mm: Introduce new vm_insert_range API

2018-12-02 Thread Souptick Joarder
Hi Mike, On Sun, Dec 2, 2018 at 4:43 PM Mike Rapoport wrote: > > On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote: > > Previouly drivers have their own way of mapping range of > > kernel pages/memory into user vma and this was done by > > invoking vm_insert_page() within a loop. >

Re: [PATCH] media: unify some sony camera sensors pattern naming

2018-12-02 Thread Bingbu Cao
On 12/01/2018 02:08 AM, Tomasz Figa wrote: Hi Bingbu, On Mon, Nov 26, 2018 at 7:56 PM wrote: From: Bingbu Cao Some Sony camera sensors have same test pattern definitions, this patch unify the pattern naming to make it more clear to the userspace. Suggested-by: Sakari Ailus Signed-off-by

Re: [PATCH v4] media: vivid: Improve timestamping

2018-12-02 Thread Arnd Bergmann
On Sun, Dec 2, 2018 at 2:47 PM Gabriel Francisco Mandaji wrote: > @@ -667,10 +653,28 @@ static void vivid_overlay(struct vivid_dev *dev, struct > vivid_buffer *buf) > } > } > > +static void vivid_cap_update_frame_period(struct vivid_dev *dev) > +{ > + u64 f_period; > + > + f

Re: [PATCH] pulse8-cec: return 0 when invalidating the logical address

2018-12-02 Thread Hans Verkuil
On 12/02/2018 04:25 PM, Torbjorn Jansson wrote: > On 2018-11-14 14:25, Hans Verkuil wrote: >> Return 0 when invalidating the logical address. The cec core produces >> a warning for drivers that do this. >> >> Signed-off-by: Hans Verkuil >> Reported-by: Torbjorn Jansson >> --- >> diff --git a/driv

Re: [PATCH] pulse8-cec: return 0 when invalidating the logical address

2018-12-02 Thread Torbjorn Jansson
On 2018-11-14 14:25, Hans Verkuil wrote: Return 0 when invalidating the logical address. The cec core produces a warning for drivers that do this. Signed-off-by: Hans Verkuil Reported-by: Torbjorn Jansson --- diff --git a/drivers/media/usb/pulse8-cec/pulse8-cec.c b/drivers/media/usb/pulse8-ce

[PATCH v4] media: vivid: Improve timestamping

2018-12-02 Thread Gabriel Francisco Mandaji
Simulate a more precise timestamp by calculating it based on the current framerate. Signed-off-by: Gabriel Francisco Mandaji --- Changes in v2: - fix spelling - end of exposure is offset by 90% of the frame period - fix timestamp calculation for FIELD_ALTERNATE (untested) - timest

Re: [PATCH v2 1/9] mm: Introduce new vm_insert_range API

2018-12-02 Thread Mike Rapoport
On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote: > Previouly drivers have their own way of mapping range of > kernel pages/memory into user vma and this was done by > invoking vm_insert_page() within a loop. > > As this pattern is common across different drivers, it can > be gener