From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jim Davis <jim.epost@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
<fengguang.wu@intel.com>,
kbuild-all@01.org
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors
Date: Wed, 2 Nov 2016 10:36:18 -0600 [thread overview]
Message-ID: <20161102103618.2600485a@vela.lan> (raw)
In-Reply-To: <87funaj9k9.fsf@intel.com>
Em Wed, 02 Nov 2016 15:27:50 +0200
Jani Nikula <jani.nikula@linux.intel.com> escreveu:
> On Wed, 02 Nov 2016, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> > Em Wed, 02 Nov 2016 13:14:47 +0200
> > Jani Nikula <jani.nikula@linux.intel.com> escreveu:
> >
> >> On Wed, 02 Nov 2016, Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote:
> >> > This series address a series of errors during PDF generation from
> >> > media documentation.
> >> >
> >> > Please notice that patch 2 carries on a PDF conversion from a PNG
> >> > image, because Sphinx is not smart enough to do the convertion.
> >> >
> >> > This is a temporary solution (That's why I'm marking this series
> >> > as RFC).
> >>
> >> This seems to work on top of docs-next.
> >
> > Yes.
> >
> >> ...but it'll break again if we include the missing admin-guide in the
> >> build. :(
> >
> > LaTeX/PDF output is ugly... for each new stuff, we need to re-validate its
> > output :-(
>
> Once we have this working, I think the only way to keep it working is to
> have continuous testing of the pdf build. That won't keep the output
> pretty, but it'll help ensure passing build.
Yes.
> Perhaps 0day could eventually start running 'make DOCBOOKS="" pdfdocs'
> after the htmldocs target? Cc: Fengguang and kbuild-all.
Good idea! it will be really helpful if Fengguang could automate the
testing process once we fix it.
Regards,
Mauro
next prev parent reply other threads:[~2016-11-02 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 22:44 Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 1/4] docs-rst: fix " Mauro Carvalho Chehab
2016-11-02 15:03 ` Markus Heiser
2016-11-02 15:06 ` Markus Heiser
2016-11-01 22:44 ` [PATCH RFC 2/4] [media] subdev-formats.rst: we need a pdf picture for bayer Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 3/4] [media] subdev-formats.rst: don't use adjustbox on a longtable Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 4/4] [media] subdev-formats.rst: add missing columns to tabularcolumns Mauro Carvalho Chehab
2016-11-01 22:53 ` [PATCH RFC 0/4] Fix PDF build errors Mauro Carvalho Chehab
2016-11-02 11:14 ` Jani Nikula
2016-11-02 12:20 ` Mauro Carvalho Chehab
2016-11-02 13:27 ` Jani Nikula
2016-11-02 16:36 ` Mauro Carvalho Chehab [this message]
2016-11-02 21:47 ` Fengguang Wu
2016-11-02 16:08 ` Markus Heiser
2016-11-02 16:47 ` Mauro Carvalho Chehab
2016-11-02 17:07 ` Markus Heiser
2016-11-03 9:11 ` Jani Nikula
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=20161102103618.2600485a@vela.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=fengguang.wu@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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
Powered by JetHome