Messages in this thread | | | Date | Sun, 25 Jan 2004 11:28:15 +0100 | From | eric.piel@tremplin ... | Subject | Re: [PATCH] Incorrect value for SIGRTMAX |
| |
Quoting George Anzinger <george@mvista.com>:
> If we are going to open this, I would like to eliminate the "MIGS_SIGEV" > stuff. If you can wait till Monday... Eliminating the special code for MIGS_SIGEV would be a great idea!
> Another issue is that this is the only place in the kernel where SIGRTMAX is > used (or it was a few months ago). If memory serves, it also seems that it > is the wrong value in at least some archs. Actually, it's not. That's exactly what the patch of Corey Minyard addressed. Half a dozen arch were corrected and now SIGRTMAX means SIGRTMAX :-)
Eric
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |