Re: posix-clock: Use an unsigned data type for a variable

2015-12-21 Thread Richard Cochran
On Mon, Dec 21, 2015 at 10:30:27AM +0100, SF Markus Elfring wrote: > > In this case, there is indeed a problem. However, just changing the > > type won't fix it. > > Would you like to explain your view on the handling of potential > data type mismatches a bit more? Yes, I will explain in the

Re: posix-clock: Use an unsigned data type for a variable

2015-12-21 Thread SF Markus Elfring
> In this case, there is indeed a problem. However, just changing the > type won't fix it. Would you like to explain your view on the handling of potential data type mismatches a bit more? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: posix-clock: Use an unsigned data type for a variable

2015-12-21 Thread Richard Cochran
On Mon, Dec 21, 2015 at 10:30:27AM +0100, SF Markus Elfring wrote: > > In this case, there is indeed a problem. However, just changing the > > type won't fix it. > > Would you like to explain your view on the handling of potential > data type mismatches a bit more? Yes, I will explain in the

Re: posix-clock: Use an unsigned data type for a variable

2015-12-21 Thread SF Markus Elfring
> In this case, there is indeed a problem. However, just changing the > type won't fix it. Would you like to explain your view on the handling of potential data type mismatches a bit more? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of