comments update for signals-document-cld_continued-notification-mechanics.patch Signed-off-by: Oleg Nesterov --- 25/kernel/signal.c~DOC_1_NOTIFY 2008-03-18 17:25:19.000000000 +0300 +++ 25/kernel/signal.c 2008-03-19 20:53:45. ...

linux-kernel - Oleg Nesterov - Mar 19 2008 - 14:20

A couple of small comments about how CLD_CONTINUED notification works. Signed-off-by: Oleg Nesterov --- 25/kernel/signal.c~DOC_NOTIFY 2008-03-10 00:11:50.000000000 +0300 +++ 25/kernel/signal.c 2008-03-10 00:47:21.000000000 ...

linux-kernel - Oleg Nesterov - Mar 9 2008 - 17:53

> A couple of small comments about how CLD_CONTINUED notification works. I'm always in favor of more good comments. > if (why) { > + /* The first thread which returns from finish_stop() ...

linux-kernel - Roland McGrath - Mar 10 2008 - 22:17

(surprisingly, this is rather important issue for me ;) On 03/10, Roland McGrath wrote: > > > if (why) { > > + /* The first thread which returns from finish_stop() > > Canonical style is: > > /* > * The first thread that returns

linux-kernel - Oleg Nesterov - Mar 11 2008 - 14:36

> Yes, I know. But the latter needs an extra line! [...] It doesn't matter what your taste is, or mine. That's why we have conventions. We just follow them and don't spend time grousing about trivia. The worst thing for a reader is to have the

linux-kernel - Roland McGrath - Mar 11 2008 - 16:28