Hi Sergio,
On 6/6/19 3:07 pm, Sergio Paracuellos wrote:
On Thu, Jun 6, 2019 at 5:06 AM Greg Ungerer wrote:
On 5/6/19 10:28 pm, Sergio Paracuellos wrote:
On Wed, Jun 5, 2019 at 7:47 AM Sergio Paracuellos
wrote:
On Wed, Jun 5, 2019 at 6:01 AM Greg Ungerer wrote:
On 4/6/19 7:36 pm, Sergio Pa
Hi Greg,
On Thu, Jun 6, 2019 at 5:06 AM Greg Ungerer wrote:
>
> Hi Sergio,
>
> On 5/6/19 10:28 pm, Sergio Paracuellos wrote:
> > On Wed, Jun 5, 2019 at 7:47 AM Sergio Paracuellos
> > wrote:
> >> On Wed, Jun 5, 2019 at 6:01 AM Greg Ungerer wrote:
> >>> On 4/6/19 7:36 pm, Sergio Paracuellos wrot
On 6/5/19 7:05 PM, Fabio Estevam wrote:
> On x86_64 when GPIOLIB is not set the following build errors
> are seen:
>
> drivers/staging/iio/addac/adt7316.c:947:3: error: implicit declaration of
> function 'gpiod_set_value' [-Werror=implicit-function-declaration]
> drivers/staging/iio/addac/adt7316
Hi Sergio,
On 5/6/19 10:28 pm, Sergio Paracuellos wrote:
On Wed, Jun 5, 2019 at 7:47 AM Sergio Paracuellos
wrote:
On Wed, Jun 5, 2019 at 6:01 AM Greg Ungerer wrote:
On 4/6/19 7:36 pm, Sergio Paracuellos wrote:
On Tue, Jun 4, 2019 at 9:14 AM Greg Ungerer wrote:
On 4/6/19 3:06 pm, Sergio Pa
G'day Fabio,
On 6/06/2019 09:42, Fabio Estevam wrote:
On x86_64 when GPIOLIB is not set the following build errors
are seen:
drivers/staging/iio/addac/adt7316.c:947:3: error: implicit declaration of
function 'gpiod_set_value' [-Werror=implicit-function-declaration]
drivers/staging/iio/addac/ad
Hi Phil,
On Wed, Jun 5, 2019 at 10:59 PM Phil Reid wrote:
> > #include
> This should be removed as well.
> See comment at top of linux/gpio.h
Good catch! Just sent a v2.
Thanks
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.l
On x86_64 when GPIOLIB is not set the following build errors
are seen:
drivers/staging/iio/addac/adt7316.c:947:3: error: implicit declaration of
function 'gpiod_set_value' [-Werror=implicit-function-declaration]
drivers/staging/iio/addac/adt7316.c:1805:2: error: implicit declaration of
function
Cleaned up the code to remove the error "(foo*)" should be "(foo *)"
reported by checkpatch from the file rtl8723bs/os_dep/ioctl_linux.c
Signed-off-by: Shobhit Kukreti
---
drivers/staging/rtl8723bs/os_dep/ioctl_linux.c | 32 +-
1 file changed, 16 insertions(+), 16 deletio
On x86_64 when GPIOLIB is not set the following build errors
are seen:
drivers/staging/iio/addac/adt7316.c:947:3: error: implicit declaration of
function 'gpiod_set_value' [-Werror=implicit-function-declaration]
drivers/staging/iio/addac/adt7316.c:1805:2: error: implicit declaration of
function
In order to print a 'size_t' type the '%zu' specifier needs to be used.
Change it accordingly in order to fix the following build warning:
drivers/staging/kpc2000/kpc_dma/fileops.c:57:35: warning: format '%ld' expects
argument of type 'long int', but argument 8 has type 'size_t {aka unsigned
in
In order to print a 'long long int' type the 'llx' specifier needs to be
used.
Change it accordingly in order to fix the following build warning:
drivers/staging/kpc2000/kpc2000/core.c:245:4: warning: format '%lx' expects
argument of type 'long unsigned int', but argument 4 has type 'long long i
Dne sreda, 05. junij 2019 ob 23:10:17 CEST je Paul Kocialkowski napisal(a):
> Hi,
>
> Le lundi 03 juin 2019 à 17:48 +0200, Jernej Škrabec a écrit :
> > Dne ponedeljek, 03. junij 2019 ob 14:18:59 CEST je Maxime Ripard
napisal(a):
> > > Hi,
> > >
> > > On Thu, May 30, 2019 at 11:15:15PM +0200, Jer
Hi Greg,
On Wed, Jun 5, 2019 at 6:37 PM Fabio Estevam wrote:
>
> In order to print a 'long long int' type the 'llx' specifier needs to be
> used.
>
> Change it accordingly in order to fix the following build warning:
>
> drivers/staging/kpc2000/kpc2000/core.c:245:4: warning: format '%lx' expects
In order to print a 'long long int' type the 'llx' specifier needs to be
used.
Change it accordingly in order to fix the following build warning:
drivers/staging/kpc2000/kpc2000/core.c:245:4: warning: format '%lx' expects
argument of type 'long unsigned int', but argument 4 has type 'long long i
In order to print a 'size_t' type the '%zu' specifier needs to be used.
Change it accordingly in order to fix the following build warning:
drivers/staging/kpc2000/kpc_dma/fileops.c:57:35: warning: format '%ld' expects
argument of type 'long int', but argument 8 has type 'size_t {aka unsigned
in
Hi,
Le lundi 03 juin 2019 à 18:37 +0200, Jernej Škrabec a écrit :
> Dne ponedeljek, 03. junij 2019 ob 14:23:28 CEST je Maxime Ripard napisal(a):
> > On Thu, May 30, 2019 at 11:15:16PM +0200, Jernej Skrabec wrote:
> > > H264 decoder driver preallocated pretty big worst case mv col buffer
> > > pool
Hi,
Le lundi 03 juin 2019 à 17:48 +0200, Jernej Škrabec a écrit :
> Dne ponedeljek, 03. junij 2019 ob 14:18:59 CEST je Maxime Ripard napisal(a):
> > Hi,
> >
> > On Thu, May 30, 2019 at 11:15:15PM +0200, Jernej Skrabec wrote:
> > > H264 and HEVC engines need additional buffers for each capture buf
Hi,
Le jeudi 30 mai 2019 à 23:15 +0200, Jernej Skrabec a écrit :
> Scale and rotation are currently not implemented, so it makes no sense to
> set chroma size for it.
>
> Signed-off-by: Jernej Skrabec
Acked-by: Paul Kocialkowski
Cheers,
Paul
> ---
> drivers/staging/media/sunxi/cedrus/cedrus
Hi,
Le jeudi 30 mai 2019 à 23:15 +0200, Jernej Skrabec a écrit :
> This array is just duplicated capture buffer queue. Remove it and adjust
> code to look into capture buffer queue instead.
>
> Signed-off-by: Jernej Skrabec
Acked-by: Paul Kocialkowski
Cheers and thanks,
Paul
> ---
> driver
Fix the following typos:
"comoponent" -> "component"
"communiction" -> "communication"
Cc: Jiri Kosina
Signed-off-by: George G. Davis
---
drivers/staging/most/Documentation/ABI/configfs-most.txt | 16
drivers/staging/most/Documentation/driver_usage.txt |
On 05/26, Jonathan Cameron wrote:
On Fri, 24 May 2019 22:26:30 -0300
Renato Lui Geh wrote:
This patch adds a YAML binding for the Analog Devices AD7780/1 and
AD7170/1 analog-to-digital converters.
Signed-off-by: Renato Lui Geh
Looks good to me, but I'm still finding my feet with these so wi
+Hridya Valsaraju
Dmitry, I filed an internal bug to track this case (b/134585943).
7aa135fcf263 didn't prevent it since your test program opens
/dev/binder0 twice and one proc instance is sending the fd to the
other proc instance. Definitely a bug in the driver (though not one
we'd ever see in a
This was reported by sparse:
drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:39:7: warning: symbol
'kpc_dma_add_device
' was not declared. Should it be static?
Signed-off-by: Valerio Genovese
---
drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletio
Hi,
Thanks for the feedback. I re-submitted the patch as v2.
best,
Valerio
Il 05/06/19 18:11, Greg KH ha scritto:
> On Wed, Jun 05, 2019 at 05:57:11PM +0200, Valerio Genovese wrote:
>> This was reported by sparse:
>> drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:39:7: warning: symbol
>> 'kpc
>This was reported by sparse:
>drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:39:7: warning: symbol
>'kpc_dma_add_device
>' was not declared. Should it be static?
>
>Signed-off-by: Valerio Genovese
>---
> drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.h | 1 +
> 1 file changed, 1 insertion(+)
>
>
On Wed, Jun 05, 2019 at 05:57:11PM +0200, Valerio Genovese wrote:
> This was reported by sparse:
> drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:39:7: warning: symbol
> 'kpc_dma_add_device
> ' was not declared. Should it be static?
>
> Signed-off-by: Valerio Genovese
> ---
> drivers/staging/
This was reported by sparse:
drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:39:7: warning: symbol
'kpc_dma_add_device
' was not declared. Should it be static?
Signed-off-by: Valerio Genovese
---
drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.h | 1 +
1 file changed, 1 insertion(+)
diff --git
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
platform_groups
head: 50aeeab171b81b604c2d3c23fc92f9fd87e40c8c
commit: 50aeeab171b81b604c2d3c23fc92f9fd87e40c8c [31/31] input: axp20x-pek:
convert platform driver to use dev_groups
config: xtensa-allyesconfig (attach
On Wed, Jun 05, 2019 at 03:53:49PM +0200, Valerio Genovese wrote:
> This was reported by sparse:
> drivers/staging/isdn/hysdn/hysdn_procconf.c:352:23: warning: symbol
> 'hysdn_proc_entry' was not declared. Should it be static?
>
> Signed-off-by: Valerio Genovese
> ---
> drivers/staging/isdn/hys
This was reported by sparse:
drivers/staging/isdn/hysdn/hysdn_procconf.c:352:23: warning: symbol
'hysdn_proc_entry' was not declared. Should it be static?
Signed-off-by: Valerio Genovese
---
drivers/staging/isdn/hysdn/hysdn_defs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
Hello dear,
We are in the market for your products after meeting at your stand during last
expo.
Please kindly send us your latest catalog and price list so as to start a new
project/order as promised during the exhibition.
I would appreciate your response about the above details required
Hi Greg,
On Wed, Jun 5, 2019 at 7:47 AM Sergio Paracuellos
wrote:
>
> Hi Greg,
>
> On Wed, Jun 5, 2019 at 6:01 AM Greg Ungerer wrote:
> >
> > Hi Sergio,
> >
> > On 4/6/19 7:36 pm, Sergio Paracuellos wrote:
> > > On Tue, Jun 4, 2019 at 9:14 AM Greg Ungerer wrote:
> > >> On 4/6/19 3:06 pm, Sergio
32 matches
Mail list logo
