All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>,
	linux-doc@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jonathan Corbet <corbet@lwn.net>,
	Markus Heiser <markus.heiser@darmarit.de>
Subject: Re: [RFC PATCH 3/3] Documentation: exclude media documentation from pdf generation
Date: Wed, 10 Aug 2016 22:05:38 +0200	[thread overview]
Message-ID: <20160810200538.GP3296@wotan.suse.de> (raw)
In-Reply-To: <2a56ee350d3b94098607ec733cde197e026f194a.1470844185.git.jani.nikula@intel.com>

On Wed, Aug 10, 2016 at 06:54:09PM +0300, Jani Nikula wrote:
> Although pdflatex is more robust than rst2pdf, building media
> documentation pdf still fails. Exclude media documentation from pdf
> generation for now.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  Documentation/conf.py | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 96b7aa66c89c..827dafc515b1 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -268,7 +268,9 @@ latex_elements = {
>  # (source start file, target name, title,
>  #  author, documentclass [howto, manual, or own class]).
>  latex_documents = [
> -    (master_doc, 'TheLinuxKernel.tex', 'The Linux Kernel Documentation',
> +    ('kernel-documentation', 'kernel-documentation.tex', 'The Linux Kernel Documentation',
> +     'The kernel development community', 'manual'),
> +    ('gpu/index', 'gpu.tex', 'Linux GPU Driver Developer\'s Guide',
>       'The kernel development community', 'manual'),

Ah so other than expanding Documentation/index.rst we also have to
edit this file. It would be good to expand the new documentation
to reflect this as this was not clear.

With these changes I confirm I get my documentation in PDF format
for the new sections I am adding!

Thanks!

  Luis

  parent reply	other threads:[~2016-08-10 20:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  1:19 Making pdfdocs with sphinx - only select rst targets Luis R. Rodriguez
2016-08-10  8:41 ` Mauro Carvalho Chehab
     [not found]   ` <CAB=NE6UUiKSn66=F+WUrqk3E1tj+fnzqFnD=dX55md6RnaiOgQ@mail.gmail.com>
2016-08-10 15:05     ` Mauro Carvalho Chehab
2016-08-10 15:54       ` [RFC PATCH 0/3] Documentation: switch to pdflatex and fix pdf build Jani Nikula
2016-08-10 15:54         ` [RFC PATCH 1/3] Documentation/sphinx: build the media intermediate rst files for all outputs Jani Nikula
2016-08-10 16:14           ` Mauro Carvalho Chehab
2016-08-10 15:54         ` [RFC PATCH 2/3] Documentation: switch to pdflatex for pdf generation Jani Nikula
2016-08-10 17:15           ` Markus Heiser
2016-08-10 20:07           ` Luis R. Rodriguez
2016-08-10 15:54         ` [RFC PATCH 3/3] Documentation: exclude media documentation from " Jani Nikula
2016-08-10 16:16           ` Mauro Carvalho Chehab
2016-08-10 16:31             ` Markus Heiser
2016-08-10 20:05           ` Luis R. Rodriguez [this message]
2016-08-10 16:27         ` [RFC PATCH 0/3] Documentation: switch to pdflatex and fix pdf build Markus Heiser
2016-08-10 20:09         ` Luis R. Rodriguez
2016-08-12 22:40         ` Jonathan Corbet
2016-08-13 16:00           ` Markus Heiser
2016-08-15  9:40           ` Jani Nikula
2016-08-15 12:17             ` Mauro Carvalho Chehab
2016-08-15 22:26               ` Mauro Carvalho Chehab
2016-08-19 12:54                 ` Jani Nikula
2016-08-19 13:21                   ` Mauro Carvalho Chehab

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=20160810200538.GP3296@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=jani.nikula@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.