Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Am 20.07.2016 um 13:27 schrieb Daniel Vetter : > On Wed, Jul 20, 2016 at 12:55 PM, Markus Heiser > wrote: >> Hi Daniel, hi Mauro, >> >> Am 19.07.2016 um 17:32 schrieb Daniel Vetter : >> >>> On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter >>> wrote: On Tue, Jul 19, 2016 at 4:59 PM, Markus

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Mauro Carvalho Chehab
Em Wed, 20 Jul 2016 14:29:01 +0200 Markus Heiser escreveu: > Am 20.07.2016 um 13:27 schrieb Daniel Vetter : > > > On Wed, Jul 20, 2016 at 12:55 PM, Markus Heiser > > wrote: > >> Hi Daniel, hi Mauro, > >> > >> Am 19.07.2016 um 17:32 schrieb Daniel Vetter : > >> > >>> On Tue, Jul 19, 2016 a

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Hi Daniel, hi Mauro, Am 19.07.2016 um 17:32 schrieb Daniel Vetter : > On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter wrote: >> On Tue, Jul 19, 2016 at 4:59 PM, Markus Heiser >> wrote: >>> >>> Am 19.07.2016 um 13:42 schrieb Daniel Vetter : >>> Unfortunately warnings generated after parsin

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Am 19.07.2016 um 13:42 schrieb Daniel Vetter : > Unfortunately warnings generated after parsing in sphinx can end up > with entirely bogus files and line numbers as sources. Strangely for > outright errors this is not a problem. Trying to convert warnings to > errors also doesn't fix it. > > The

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-20 Thread Daniel Vetter
On Wed, Jul 20, 2016 at 12:55 PM, Markus Heiser wrote: > Hi Daniel, hi Mauro, > > Am 19.07.2016 um 17:32 schrieb Daniel Vetter : > >> On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter >> wrote: >>> On Tue, Jul 19, 2016 at 4:59 PM, Markus Heiser >>> wrote: Am 19.07.2016 um 13:42 schrieb D

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-19 Thread Jonathan Corbet
On Tue, 19 Jul 2016 13:42:54 +0200 Daniel Vetter wrote: > Unfortunately warnings generated after parsing in sphinx can end up > with entirely bogus files and line numbers as sources. Strangely for > outright errors this is not a problem. Trying to convert warnings to > errors also doesn't fix it.

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-19 Thread Daniel Vetter
On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter wrote: > On Tue, Jul 19, 2016 at 4:59 PM, Markus Heiser > wrote: >> >> Am 19.07.2016 um 13:42 schrieb Daniel Vetter : >> >>> Unfortunately warnings generated after parsing in sphinx can end up >>> with entirely bogus files and line numbers as sources

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-19 Thread Daniel Vetter
On Tue, Jul 19, 2016 at 4:59 PM, Markus Heiser wrote: > > Am 19.07.2016 um 13:42 schrieb Daniel Vetter : > >> Unfortunately warnings generated after parsing in sphinx can end up >> with entirely bogus files and line numbers as sources. Strangely for >> outright errors this is not a problem. Trying

[Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-19 Thread Daniel Vetter
Unfortunately warnings generated after parsing in sphinx can end up with entirely bogus files and line numbers as sources. Strangely for outright errors this is not a problem. Trying to convert warnings to errors also doesn't fix it. The only way to get useful output out of sphinx to be able to ro