On Wed, 1 May 2013 09:56:13 -0400 Robert Love wrote:
> Don't acquire ashmem_mutex in ashmem_shrink if we've somehow recursed into the
> shrinker code from within ashmem. Just bail out, avoiding a deadlock. This is
> fine, as ashmem cache pruning is advisory anyhow.
>
Sorry, but I don't think "
From: Wei Yongjun
Fix to return -EINVAL in the i2c device found error handling
case instead of 0, as done elsewhere in this function.
And also correct the fail1 and fail2 lable to do the right thing.
Signed-off-by: Wei Yongjun
---
drivers/staging/iio/light/tsl2x7x_core.c | 9 +
1 file
Hi,
I'm running OpenSuSE 12.3, kernel 3.7.
I found out that the problem occurs when there is another card in the VME-crate
that performs a lot of writes in the memory-region I'm reading in my example.
('a lot of' = each millisecond, the first 64 bytes get updated).
I've already added a sleep to
On 07/05/13 10:54, Martyn Welch wrote:
> On 06/05/13 09:45, De Roo, Steven wrote:
>> Hi all,
>>
>> I'm running OpenSuSE 12.3, kernel 3.7.
>>
>
> I'm not aware of any changes between 3.7 and 3.9 that would affect the
> behaviour of the driver (mainly cosmetic changes), so I'm not sure it's worth
>
Hi all,
I'm running OpenSuSE 12.3, kernel 3.7.
I found out that the problem occurs when there is another card in the VME-crate
that performs a lot of writes in the memory-region I'm reading in my example.
('a lot of' = each millisecond, the first 64 bytes get updated).
I've already added a sleep
On Mon, May 06, 2013 at 12:21:39PM +0530, Srinidhi Kasagar wrote:
> > > > - regulator_enable(rmi4_data->regulator);
> > > > + retval = regulator_enable(rmi4_data->regulator);
> > > > + if (retval < 0)
> > > > + return retval;
> > > Does it make sense to add a dev_err
On 3 May 2013 18:06, Eduardo Valentin wrote:
> On 03-05-2013 01:52, Sachin Kamat wrote:
>> Use IS_ERR instead of IS_ERR_OR_NULL on clk_get results.
>>
>> Signed-off-by: Sachin Kamat
>> Cc: Eduardo Valentin
>> ---
>
> Sachin,
>
>
> I have a patch that covers this already:
>
> https://patchwork.ke
From: Wei Yongjun
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Signed-off-by: Wei Yongjun
---
drivers/staging/media/davinci_vpfe/vpfe_mc_capture.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/dri
On 2013-05-03 21:39, H Hartley Sweeten wrote:
Since the merge window is now open, this series is posted as an RFC.
Any comments would be appreciated. I'm hoping to get any issues
addressed so the series will be ready when the staging tree is
opened after the merge window closes.
This comedi driv
On 06/05/13 09:45, De Roo, Steven wrote:
> Hi all,
>
> I'm running OpenSuSE 12.3, kernel 3.7.
>
I'm not aware of any changes between 3.7 and 3.9 that would affect the
behaviour of the driver (mainly cosmetic changes), so I'm not sure it's worth
trying 3.9...
> I found out that the problem occur
On 2013-05-03 21:50, H Hartley Sweeten wrote:
When this driver is converted to the comedi (*auto_attach) mechanism
the device reset will be done during the (*auto_attach). To make the
conversion cleaner, factor the device reset out of the (*probe).
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbot
For NUL terminated string, need always let it ended by zero.
The 'name' may be copied to user mode ('dvb_fe->ops.info' is 'struct
dvb_frontend_info' which is defined in ./include/uapi/...), and its
length is also known within as102_dvb_register_fe(), so need fully
initialize it (not use strlcpy i
Hi Wei,
Thanks for the patch.
On Tue, May 7, 2013 at 5:21 PM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return a negative error code from the error handling
> case instead of 0, as done elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
Acked-by: Lad, Prabhakar
Regards,
--Pr
On Sun, May 05, 2013 at 16:18:55 +0200, Dan Carpenter wrote:
> On Fri, May 03, 2013 at 12:37:14PM +0530, Srinidhi Kasagar wrote:
> > On Thu, May 02, 2013 at 17:48:10 +0200, Lee Jones wrote:
> > > drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c:
> > > In function ‘synaptics_rmi4_resume’:
> > >
Hi Martyn,
It turns out that my SBC was configured as a system controller...
The result: it allowed access to the bus, where it shouldn't.
This way, 2 VME-boards were simultaneously modifying the address-lines,
causing a corrupt VME-address, resulting in a BERR bus error.
Kind regards,
& many th
Dear all,
Does anybody now how to configure ROR (Release On Request) or RWD (Release When
Done)
using the 'vme_user' module on a XVME-6300 SBC with TSI148 chipset ?
kind regards,
Steven De Roo
___
devel mailing list
devel@linuxdriverproject.org
http:/
Avoid waking up every thread sleeping in a binder call during
suspend and resume by calling a freezable blocking call. Previous
patches modified the freezer to avoid sending wakeups to threads
that are blocked in freezable blocking calls.
This call was selected to be converted to a freezable call
Am I correct that using ROR would improve performance ?
Steven
On 07/05/13 16:10, De Roo, Steven wrote:
> Dear all,
>
> Does anybody now how to configure ROR (Release On Request) or RWD
> (Release When Done) using the 'vme_user' module on a XVME-6300 SBC with
> TSI148 chipset ?
>
> kind rega
On 07/05/13 17:06, De Roo, Steven wrote:
> Am I correct that using ROR would improve performance ?
>
> Steven
>
I assume that it would depend on the use case.
Martyn
>
> On 07/05/13 16:10, De Roo, Steven wrote:
>> Dear all,
>>
>> Does anybody now how to configure ROR (Release On Request) or R
On 07/05/13 16:10, De Roo, Steven wrote:
> Dear all,
>
> Does anybody now how to configure ROR (Release On Request) or RWD (Release
> When Done)
> using the 'vme_user' module on a XVME-6300 SBC with TSI148 chipset ?
>
> kind regards,
> Steven De Roo
>
The tsi148 driver doesn't currently suppo
20 matches
Mail list logo
