linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: 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>
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors
Date: Tue, 1 Nov 2016 16:53:02 -0600	[thread overview]
Message-ID: <20161101165302.193b1406@vela.lan> (raw)
In-Reply-To: <cover.1478040090.git.mchehab@osg.samsung.com>

Em Tue,  1 Nov 2016 16:44:09 -0600
Mauro Carvalho Chehab <mchehab@osg.samsung.com> escreveu:

> 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).
> 
> I'm working on a more permanent access where the image format

In time:
	"more permanent solution"

> required by Sphinx for PDF output will be met.
> 
> Mauro Carvalho Chehab (4):
>   docs-rst: fix PDF build errors
>   [media] subdev-formats.rst: we need a pdf picture for bayer
>   [media] subdev-formats.rst: don't use adjustbox on a longtable
>   [media] subdev-formats.rst: add missing columns to tabularcolumns
> 
>  Documentation/conf.py                                  |   4 ++++
>  Documentation/media/index.rst                          |   5 -----
>  Documentation/media/uapi/v4l/subdev-formats.rst        |  17 +++++++++++------
>  .../media/uapi/v4l/subdev-formats_files/bayer.pdf      | Bin 0 -> 11131 bytes
>  4 files changed, 15 insertions(+), 11 deletions(-)
>  create mode 100644 Documentation/media/uapi/v4l/subdev-formats_files/bayer.pdf
> 




Cheers,
Mauro

  parent reply	other threads:[~2016-11-01 22:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01 22:44 [PATCH RFC 0/4] Fix PDF build errors 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 ` Mauro Carvalho Chehab [this message]
2016-11-02 11:14 ` [PATCH RFC 0/4] Fix PDF build errors 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
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=20161101165302.193b1406@vela.lan \
    --to=mchehab@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jim.epost@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).