[PATCH] usbip: handle length at sysfs show() functions

From: Márton Németh The sysfs show() functions shall return the actual content length of the result buffer. According to Documentation/filesystems/sysfs.txt:215 the scnprintf() function is preferred. See also the article titled "snprintf() confusion" at http://lwn.net/Articles/69419/ . Signed-o

透彻掌握三大财务报表1有效掌控企业经营大局

N|ÀÏ°å¼°×ܾ­ÀíºËÐIJÆÎñ¹ÜÀíʵս||| 116.203.151.245 Dwpgyu5787.xls Description: Binary data ___ devel mailing list devel@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Re: [PATCH] staging: intel_sst: Fix memory leak

On Tue, May 31, 2011 at 09:03:56PM +0200, Andre Bartke wrote: > In case of an error stream_bufs is not freed here. > > Signed-off-by: Andre Bartke > --- > .../staging/intel_sst/intel_sst_app_interface.c|4 +++- > 1 files changed, 3 insertions(+), 1 deletions(-) > > diff --git a/drivers/

[PATCH] staging/hv: Fix memory leak of storvsc_dev_add()

stor_device is not freed in storvsc_dev_add() causing a memory leak in case of an allocation error. Signed-off-by: Andre Bartke --- drivers/staging/hv/storvsc.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/staging/hv/storvsc.c b/drivers/staging/hv/storvsc.c in

Re: [PATCH 2/2] staging/iio: Make IIO depend on GENERIC_HARDIRQS

On Tue, May 31, 2011 at 13:01, jonathan.came...@gmail.com wrote: > Geert Uytterhoeven wrote: >>On m68k (which doesn't support generic hardirqs yet): [...] >>Hence IIO_TRIGGER should depend on GENERIC_HARDIRQS. >>But as IIO_TRIGGER and IIO_RING_BUFFER form a maze of dependencies and >>selects, >

[PATCH] staging: intel_sst: Fix memory leak

In case of an error stream_bufs is not freed here. Signed-off-by: Andre Bartke --- .../staging/intel_sst/intel_sst_app_interface.c|4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/drivers/staging/intel_sst/intel_sst_app_interface.c b/drivers/staging/intel_sst/intel

Hello Would You Like To Earn

Hello devel Would you like to earn an extra $200 everyday?, for just 45 minutes work? You could quit your job and make double the money at home working for yourself. visit->http:tinyurl.com/3brnlpx Regards, Sharon Burns Survey Human Resources Dept. __

Re: [PATCH 2/2] staging/iio: Make IIO depend on GENERIC_HARDIRQS

Geert Uytterhoeven wrote: >On m68k (which doesn't support generic hardirqs yet): > >drivers/staging/iio/industrialio-trigger.c: In function >‘iio_trigger_poll’: >drivers/staging/iio/industrialio-trigger.c:180: error: implicit >declaration of function ‘generic_handle_irq’ >drivers/staging/iio/in

[PATCH 2/2] staging/iio: Make IIO depend on GENERIC_HARDIRQS

On m68k (which doesn't support generic hardirqs yet): drivers/staging/iio/industrialio-trigger.c: In function ‘iio_trigger_poll’: drivers/staging/iio/industrialio-trigger.c:180: error: implicit declaration of function ‘generic_handle_irq’ drivers/staging/iio/industrialio-trigger.c: In function ‘

Re: Janitor-Question: use __set_bit instead of |=

On 05/30/2011 11:23 PM, Peter Hüwe wrote: > Hi Janitors, staging-list > > what is your opinion on using set_bit instead of using |= to set a bit? > Is it worth the effort to convert existing |= to set_bit? > > __set_bit > pro: > - often implemented in optimized assembly (e.g. for x86) > - intent

[PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver.

This patch adds the pruss MFD driver and associated include files. For details regarding the PRUSS please refer the folowing link: http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit_Subsystem The rational behind the MFD driver being the fact that multiple devices can be implemented

Re: Janitor-Question: use __set_bit instead of |=

Am 30.05.2011 23:23, schrieb Peter Hüwe: > Hi Janitors, staging-list > > what is your opinion on using set_bit instead of using |= to set a bit? > Is it worth the effort to convert existing |= to set_bit? > > __set_bit > pro: > - often implemented in optimized assembly (e.g. for x86) > - inten