On Fri, Oct 11, 2013 at 11:26:05AM +0900, hyunhee.kim wrote:
> The regulator haptic driver function can be used to control motor by on/off
> regulator.
> User can control the haptic driver by using force feedback framework.
>
> Signed-off-by: Hyunhee Kim
> Signed-off-by: Kyungmin Park
> ---
>
Hi Hyunhee,
On Fri, Oct 11, 2013 at 11:26:05AM +0900, hyunhee.kim wrote:
> +static void regulator_haptic_work(struct work_struct *work)
> +{
> + struct regulator_haptic *haptic = container_of(work,
> +struct
> regulator_haptic,
you got a
Hi Hyunhee,
On Fri, Oct 11, 2013 at 11:26:05AM +0900, hyunhee.kim wrote:
+static void regulator_haptic_work(struct work_struct *work)
+{
+ struct regulator_haptic *haptic = container_of(work,
+struct
regulator_haptic,
you got a line
On Fri, Oct 11, 2013 at 11:26:05AM +0900, hyunhee.kim wrote:
The regulator haptic driver function can be used to control motor by on/off
regulator.
User can control the haptic driver by using force feedback framework.
Signed-off-by: Hyunhee Kim hyunhee@samsung.com
Signed-off-by:
> This is a uniprocessor AMD64 system running software RAID-5 and RAID-10
> over multiple PCIe SiI3132 SATA controllers. The hardware has been very
> stable for a long time, but has been acting up of late since I upgraded
> to 2.6.20.3. ECC memory should preclude the possibility of bit-flip
>
This is a uniprocessor AMD64 system running software RAID-5 and RAID-10
over multiple PCIe SiI3132 SATA controllers. The hardware has been very
stable for a long time, but has been acting up of late since I upgraded
to 2.6.20.3. ECC memory should preclude the possibility of bit-flip
errors.
> Would another possible trace look like this?
>
> idr_remove called for id=1 which is not allocated.
> [] dump_trace+0x69/0x1af
> [] show_trace_log_lvl+0x18/0x2c
> [] show_trace+0xf/0x11
> [] dump_stack+0x15/0x17
> [] idr_remove+0xe2/0x143
> [] release_dev+0x63b/0x652
> []
] chrdev_open+0x0/0x180
[] __dentry_open+0xc9/0x210
[] do_filp_open+0x5c/0x70
[] get_unused_fd+0x61/0xd0
[] do_sys_open+0x53/0x100
[] sys_open+0x27/0x30
[] syscall_call+0x7/0xb
using this test application available on:
http://www.ruivo.org/~aris/pty_sodomizer.c
Signed-off-by: Aristeu Se
/pty_sodomizer.c
Signed-off-by: Aristeu Sergio Rozanski Filho [EMAIL PROTECTED]
Index: linus-2.6/drivers/char/tty_io.c
===
--- linus-2.6.orig/drivers/char/tty_io.c
+++ linus-2.6/drivers/char/tty_io.c
@@ -1901,6 +1901,20 @@ static int
Would another possible trace look like this?
idr_remove called for id=1 which is not allocated.
[c0403f10] dump_trace+0x69/0x1af
[c040406e] show_trace_log_lvl+0x18/0x2c
[c04045e9] show_trace+0xf/0x11
[c0404673] dump_stack+0x15/0x17
[c04d3fcb] idr_remove+0xe2/0x143
[c051ee50]
Hi,
for some time I was unable to use Atheros based cards on my
notebook (O2Micro oz6812 Cardbus controller) because of lots
of rx packets getting dropped by frame errors. running ping I got
this: (~1m from access point)
PING 192.168.67.1 (192.168.67.1): 56 data
Hi,
for some time I was unable to use Atheros based cards on my
notebook (O2Micro oz6812 Cardbus controller) because of lots
of rx packets getting dropped by frame errors. running ping I got
this: (~1m from access point)
PING 192.168.67.1 (192.168.67.1): 56 data
Hi,
> On the same path sk_set_owner also gets called twice, I think this
> causes double module use count when creating sockets. Module use count
> need some attention all over x25.
I'm working on it already. I hope to send patches soon.
Is linux-x25 list alive? if not, perhaps we should add
Hi,
On the same path sk_set_owner also gets called twice, I think this
causes double module use count when creating sockets. Module use count
need some attention all over x25.
I'm working on it already. I hope to send patches soon.
Is linux-x25 list alive? if not, perhaps we should add netdev
14 matches
Mail list logo
