From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Fix PDF builds on media documentation
Date: Tue, 08 Nov 2016 11:04:23 +0200 [thread overview]
Message-ID: <87vavy736w.fsf@intel.com> (raw)
In-Reply-To: <cover.1478531459.git.mchehab@s-opensource.com>
On Mon, 07 Nov 2016, Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> This series address a series of errors during PDF generation from
> media documentation.
I'm missing patches 3-6 of this series, and so is the archive.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-11-08 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 15:20 [PATCH v2 0/6] Fix PDF builds on media documentation Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 1/6] docs-rst: fix LaTeX \DURole renewcommand with Sphinx 1.3+ Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 2/6] [media] subdev-formats.rst: don't use adjustbox on a longtable Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 3/6] [media] subdev-formats.rst: add missing columns to tabularcolumns Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 4/6] [media] convert some images from png to svg Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 5/6] [media] docs-rst: convert gif files to png Mauro Carvalho Chehab
2016-11-07 15:20 ` [PATCH v2 6/6] [media] docs-rst: auto-generate PDF image files Mauro Carvalho Chehab
2016-11-08 9:04 ` Jani Nikula [this message]
2016-11-08 9:04 ` [PATCH v2 0/6] Fix PDF builds on media documentation Jani Nikula
2016-11-08 9:19 ` Mauro Carvalho Chehab
2016-11-08 9:56 ` 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=87vavy736w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.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).