Re: [PATCHv2 1/9] mm: Introduce new vm_insert_range and vm_insert_range_buggy API

2019-02-07 Thread Mike Rapoport
On Thu, Feb 07, 2019 at 09:37:08PM +0530, Souptick Joarder wrote: > On Thu, Feb 7, 2019 at 9:27 PM Mike Rapoport wrote: > > > > Hi Souptick, > > > > On Thu, Feb 07, 2019 at 09:19:47PM +0530, Souptick Joarder wrote: > > > Hi Mike, > > > > > >

Re: [PATCHv2 1/9] mm: Introduce new vm_insert_range and vm_insert_range_buggy API

2019-02-07 Thread Mike Rapoport
Hi Souptick, On Thu, Feb 07, 2019 at 09:19:47PM +0530, Souptick Joarder wrote: > Hi Mike, > > Just thought to take opinion for documentation before placing it in v3. > Does it looks fine ? Overall looks good to me. Several minor points below. > +/** > + * __vm_insert_range - insert range of ke

Re: [PATCHv2 1/9] mm: Introduce new vm_insert_range and vm_insert_range_buggy API

2019-01-31 Thread Mike Rapoport
On Thu, Jan 31, 2019 at 03:43:39PM +0530, Souptick Joarder wrote: > On Thu, Jan 31, 2019 at 2:09 PM Mike Rapoport wrote: > > > > On Thu, Jan 31, 2019 at 08:38:12AM +0530, Souptick Joarder wrote: > > > Previouly drivers have their own way of mapping range of > > >

Re: [PATCHv2 1/9] mm: Introduce new vm_insert_range and vm_insert_range_buggy API

2019-01-31 Thread Mike Rapoport
On Thu, Jan 31, 2019 at 08:38:12AM +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

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 rang

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

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

2018-11-22 Thread Mike Rapoport
On Mon, Nov 19, 2018 at 11:15:15PM +0530, Souptick Joarder wrote: > On Mon, Nov 19, 2018 at 9:56 PM Mike Rapoport wrote: > > > > On Mon, Nov 19, 2018 at 08:43:09PM +0530, Souptick Joarder wrote: > > > Hi Mike, > > > > > > On Sat, Nov 17, 20

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

2018-11-19 Thread Mike Rapoport
On Mon, Nov 19, 2018 at 08:43:09PM +0530, Souptick Joarder wrote: > Hi Mike, > > On Sat, Nov 17, 2018 at 8:07 PM Matthew Wilcox wrote: > > > > On Sat, Nov 17, 2018 at 12:26:38PM +0530, Souptick Joarder wrote: > > > On Fri, Nov 16, 2018 at

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

2018-11-16 Thread Mike Rapoport
On Thu, Nov 15, 2018 at 09:15:30PM +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

Re: rt-mutex usage in i2c

2015-03-15 Thread Mike Rapoport
On Sat, Mar 14, 2015 at 1:32 PM, Wolfram Sang wrote: > On Sat, Mar 14, 2015 at 12:27:03PM +0100, Wolfram Sang wrote: >> Hi Sebastian, >> >> > - i2c_transfer() has this piece: >> > 2091 if (in_atomic() || irqs_disabled()) { >> > 2092 ret = i2c_trylock_ada

Re: Bug in AMDs V4L2 driver lxv4l2?

2010-05-17 Thread Mike Rapoport
Hi Daniel, Daniel Borkmann wrote: Hi everyone, I am using an AMD Geode webcam with a V4L driver (lxv4l2). For the userspace I've implemented a V4L binding with memory mapping of the frames. After sucessfull receiving frames it lasts about two or three minutes and then either the timestamp of

Re: [PATCH 1/3] em-x270: don't use pxa_camera init() callback

2009-11-17 Thread Mike Rapoport
Antonio Ospite wrote: > pxa_camera init() is going to be removed. > > Signed-off-by: Antonio Ospite > --- > arch/arm/mach-pxa/em-x270.c |9 + > 1 files changed, 5 insertions(+), 4 deletions(-) Acked-by: Mike Rapoport > diff --git a/arch/arm/mach-pxa/em-x

Re: [PATCH] Add RGB555X and RGB565X formats to pxa-camera

2009-09-05 Thread Mike Rapoport
Hi Guennadi, Guennadi Liakhovetski wrote: > On Mon, 3 Aug 2009, Mike Rapoport wrote: > >>> 2. Mike, while reviewing this patch I came across code in >>> pxa_camera_setup_cicr(), introduced by your earlier patch: >>> >>> case V4L2_PIX_FMT_RGB555: &g

Re: [PATCH] Add RGB555X and RGB565X formats to pxa-camera

2009-08-03 Thread Mike Rapoport
Guennadi Liakhovetski wrote: > On Mon, 3 Aug 2009, Eric Miao wrote: > >> Marek Vasut wrote: >>> Hi! >>> >>> Eric, would you mind applying ? >>> >>> From 4dcbff010e996f4c6e5761b3c19f5d863ab51b39 Mon Sep 17 00:00:00 2001 >>> From: Marek Vasut >>> Date: Mon, 3 Aug 2009 10:27:57 +0200 >>> Subject: