* about X and VT_WAITACTIVE
@ 2009-06-19 2:14 tommy
2009-06-19 2:41 ` tommy
0 siblings, 1 reply; 2+ messages in thread
From: tommy @ 2009-06-19 2:14 UTC (permalink / raw)
To: spock.DeleteThis; +Cc: linux-arm-kernel, linux-kernel
hi,Dear Sir!
First thanks to your patch by
http://forum.soft32.com/linux/PATCH-vt-fix-potential-race-VT_WAITACTIVE-handler-ftopict341520.html!
But Now I also met this question by VT_WAITACTIVATE!
My board is S3C6410 ARM11,Xorg-server-1.3.0.0,linux 2.6.24
linux/driver/char/vt_ioctl also have your patch code for
VT_WAITACTIVATE.
I met VT_WAITACTIVATE question by 3/50 testing my rootfs on ARM11
S3C6410.
How can i fix this ?thanks !
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: about X and VT_WAITACTIVE
2009-06-19 2:14 about X and VT_WAITACTIVE tommy
@ 2009-06-19 2:41 ` tommy
0 siblings, 0 replies; 2+ messages in thread
From: tommy @ 2009-06-19 2:41 UTC (permalink / raw)
To: linux-arm-kernel, linux-kernel@vger.kernel.org
hi,all !
i have found this patch in
http://kerneltrap.org/mailarchive/linux-kernel/2007/5/30/97252!
i think its codestyle is better than former!
anyone agree ?
On 五, 2009-06-19 at 10:14 +0800, tommy wrote:
> hi,Dear Sir!
>
> First thanks to your patch by
> http://forum.soft32.com/linux/PATCH-vt-fix-potential-race-VT_WAITACTIVE-handler-ftopict341520.html!
>
> But Now I also met this question by VT_WAITACTIVATE!
>
> My board is S3C6410 ARM11,Xorg-server-1.3.0.0,linux 2.6.24
>
> linux/driver/char/vt_ioctl also have your patch code for
> VT_WAITACTIVATE.
>
> I met VT_WAITACTIVATE question by 3/50 testing my rootfs on ARM11
> S3C6410.
>
> How can i fix this ?thanks !
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-06-19 2:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-19 2:14 about X and VT_WAITACTIVE tommy
2009-06-19 2:41 ` tommy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox