On Wed, Feb 11, 2015 at 3:33 AM, Takashi Iwai wrote:
> At Tue, 10 Feb 2015 23:03:12 -0600,
> Chris Rorvick wrote:
>>
>> Use explicit types to reflect the range of valid values.
>
> Well, this isn't necessarily to be changed at these places. If we
> want to be safer, there should be proper range
At Tue, 10 Feb 2015 23:03:12 -0600,
Chris Rorvick wrote:
>
> Use explicit types to reflect the range of valid values.
Well, this isn't necessarily to be changed at these places. If we
want to be safer, there should be proper range checks instead.
Also, readers may wonder when they see the
At Tue, 10 Feb 2015 23:03:12 -0600,
Chris Rorvick wrote:
Use explicit types to reflect the range of valid values.
Well, this isn't necessarily to be changed at these places. If we
want to be safer, there should be proper range checks instead.
Also, readers may wonder when they see the
On Wed, Feb 11, 2015 at 3:33 AM, Takashi Iwai ti...@suse.de wrote:
At Tue, 10 Feb 2015 23:03:12 -0600,
Chris Rorvick wrote:
Use explicit types to reflect the range of valid values.
Well, this isn't necessarily to be changed at these places. If we
want to be safer, there should be proper
Use explicit types to reflect the range of valid values.
Signed-off-by: Chris Rorvick
---
sound/usb/line6/driver.c | 10 +-
sound/usb/line6/driver.h | 8
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/sound/usb/line6/driver.c b/sound/usb/line6/driver.c
index
Use explicit types to reflect the range of valid values.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
sound/usb/line6/driver.c | 10 +-
sound/usb/line6/driver.h | 8
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/sound/usb/line6/driver.c
6 matches
Mail list logo
