public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Markus Heiser <markus.heiser@darmarit.de>,
	linux-doc@vger.kernel.org,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/2] doc/sphinx: Enable keep_warnings
Date: Tue, 19 Jul 2016 16:23:12 -0600	[thread overview]
Message-ID: <20160719162312.692230e7@lwn.net> (raw)
In-Reply-To: <1468928575-11309-1-git-send-email-daniel.vetter@ffwll.ch>

On Tue, 19 Jul 2016 13:42:54 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> 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.
> 
> The only way to get useful output out of sphinx to be able to root
> cause the error seems to be enabling keep_warnings, which inserts
> a System Message into the actual output. Not pretty at all, but I
> don't really want to fix up core rst/sphinx code, and this gets the job
> done meanwhile.

I'll go ahead and apply this.  It *would* be nice, someday, to figure out
how to get proper info out for warnings directly, but until somebody gets
there...

Thanks,

jon

      parent reply	other threads:[~2016-07-19 22:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 11:42 [PATCH 1/2] doc/sphinx: Enable keep_warnings Daniel Vetter
2016-07-19 11:42 ` [PATCH 2/2] drm/doc: Fix more kerneldoc/sphinx warnings Daniel Vetter
2016-07-19 12:36   ` Daniel Vetter
2016-07-20 12:20     ` Mauro Carvalho Chehab
2016-07-20 18:35       ` Markus Heiser
2016-07-20 20:48         ` Mauro Carvalho Chehab
2016-07-22 15:06         ` Mauro Carvalho Chehab
2016-07-19 11:49 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] doc/sphinx: Enable keep_warnings Patchwork
2016-07-19 14:59 ` [PATCH 1/2] " Markus Heiser
2016-07-19 15:25   ` Daniel Vetter
2016-07-19 15:32     ` Daniel Vetter
2016-07-20 10:55       ` Markus Heiser
2016-07-20 11:27         ` Daniel Vetter
2016-07-20 12:29           ` Markus Heiser
2016-07-20 12:49             ` Mauro Carvalho Chehab
2016-07-19 22:23 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160719162312.692230e7@lwn.net \
    --to=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox