[PATCH v2 1/1] drm: modes: fix DRM modes analysis regression

2015-12-10 Thread Daniel Vetter
On Wed, Dec 09, 2015 at 08:11:39PM +0100, Corentin LABBE wrote: > Le 09/12/2015 16:32, Jani Nikula a écrit : > > On Wed, 09 Dec 2015, LABBE Corentin wrote: > >> My latest commit introduce some case where a valid mode, could be > >> rejected. > >> simple_strtox functions stop at first non-digit ch

[PATCH v2 1/1] drm: modes: fix DRM modes analysis regression

2015-12-09 Thread Corentin LABBE
Le 09/12/2015 16:32, Jani Nikula a écrit : > On Wed, 09 Dec 2015, LABBE Corentin wrote: >> My latest commit introduce some case where a valid mode, could be >> rejected. >> simple_strtox functions stop at first non-digit character, but kstrtox not. >> So args like "video=HDMI-A-1:720x480-16 at 60

[PATCH v2 1/1] drm: modes: fix DRM modes analysis regression

2015-12-09 Thread Jani Nikula
On Wed, 09 Dec 2015, LABBE Corentin wrote: > My latest commit introduce some case where a valid mode, could be > rejected. > simple_strtox functions stop at first non-digit character, but kstrtox not. > So args like "video=HDMI-A-1:720x480-16 at 60" will be reject when checking > 16 at . > The pr

[PATCH v2 1/1] drm: modes: fix DRM modes analysis regression

2015-12-09 Thread LABBE Corentin
My latest commit introduce some case where a valid mode, could be rejected. simple_strtox functions stop at first non-digit character, but kstrtox not. So args like "video=HDMI-A-1:720x480-16 at 60" will be reject when checking 16 at . The proper solution is to store digits in a specific buffer.