On Thu, Apr 18, 2013 at 07:40:16AM +, 송은봉 wrote:
>
> I rewrite my patch because the patch before i sent have many white space.
> Thanks!
This should have been below the "---" after the sigend-off.
> ---
> I've been debugging the abnormal operation of i2c on octeon.
> If a process is
On Thu, Apr 18, 2013 at 07:40:16AM +, 송은봉 wrote:
I rewrite my patch because the patch before i sent have many white space.
Thanks!
This should have been below the --- after the sigend-off.
---
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by
I rewrite my patch because the patch before i sent have many white space.
Thanks!
---
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed
I rewrite my patch because the patch before i sent have many white space.
Thanks!
---
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed
>Basically OK, but you have lots of whitespace issues, so I can't apply
>your patch. Please resend and make sure it applies.
Sorry, I rewrite my patch here.
Signed-off-by: EunBong Song
---
drivers/i2c/busses/i2c-octeon.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff
On Tue, Feb 26, 2013 at 09:08:43PM +, 송은봉 wrote:
>
> I've been debugging the abnormal operation of i2c on octeon.
> If a process is terminated by signal in the middle of i2c operation,
> next i2c read operation which is done by another process was failed.
> So i changed to ignore signal in
On Tue, Feb 26, 2013 at 09:08:43PM +, 송은봉 wrote:
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed to ignore signal in the
Basically OK, but you have lots of whitespace issues, so I can't apply
your patch. Please resend and make sure it applies.
Sorry, I rewrite my patch here.
Signed-off-by: EunBong Song eunb.s...@samsung.com
---
drivers/i2c/busses/i2c-octeon.c |8
1 files changed, 4 insertions(+), 4
On Tue, Feb 26, 2013 at 4:37 PM, Wolfram Sang wrote:
> On Tue, Feb 26, 2013 at 11:02:17AM +0100, Jiri Kosina wrote:
>> On Fri, 22 Feb 2013, 송은봉 wrote:
>>
>> >
>> >
>> >
>> > I've been debugging the abnormal operation of i2c on octeon.
>> > If a process is terminated by signal in the middle of i2c
On Tue, Feb 26, 2013 at 4:37 PM, Wolfram Sang w...@the-dreams.de wrote:
On Tue, Feb 26, 2013 at 11:02:17AM +0100, Jiri Kosina wrote:
On Fri, 22 Feb 2013, 송은봉 wrote:
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c
>If the wait is not interruptible, I think you will not be able to 'kill
>-9' a userspace process blocked here.
As your words. the process will not be killed immediately, but after timeout(2
jiffies) it will be killed.
I think that delay is acceptable.
--- Original Message ---
Sender
On 02/26/2013 12:54 PM, 송은봉 wrote:
> I've been debugging the abnormal operation of i2c on octeon.
> If a process is terminated by signal in the middle of i2c operation,
> next i2c read operation which is done by another process was failed.
> So i changed to ignore signal in the middle of i2c
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed to ignore signal in the middle of i2c operation.
After that the problem was not
On Tue, Feb 26, 2013 at 11:02:17AM +0100, Jiri Kosina wrote:
> On Fri, 22 Feb 2013, 송은봉 wrote:
>
> >
> >
> >
> > I've been debugging the abnormal operation of i2c on octeon.
> > If a process is terminated by signal in the middle of i2c operation,
> > next i2c read operation which is done by
On Fri, 22 Feb 2013, 송은봉 wrote:
>
>
>
> I've been debugging the abnormal operation of i2c on octeon.
> If a process is terminated by signal in the middle of i2c operation,
> next i2c read operation which is done by another process was failed.
> So i changed to ignore signal in the middle of
On Fri, 22 Feb 2013, 송은봉 wrote:
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed to ignore signal in the middle of i2c
On Tue, Feb 26, 2013 at 11:02:17AM +0100, Jiri Kosina wrote:
On Fri, 22 Feb 2013, 송은봉 wrote:
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed to ignore signal in the middle of i2c operation.
After that the problem was not
On 02/26/2013 12:54 PM, 송은봉 wrote:
I've been debugging the abnormal operation of i2c on octeon.
If a process is terminated by signal in the middle of i2c operation,
next i2c read operation which is done by another process was failed.
So i changed to ignore signal in the middle of i2c
If the wait is not interruptible, I think you will not be able to 'kill
-9' a userspace process blocked here.
As your words. the process will not be killed immediately, but after timeout(2
jiffies) it will be killed.
I think that delay is acceptable.
--- Original Message ---
Sender :
20 matches
Mail list logo
