Re: [PATCH] Incorrect value for SIGRTMAX

[eric . piel]

Quoting George Anzinger <george@xxxxxxxxxx>:

> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/