On Sun, Jun 18, 2017 at 05:46:25PM -0600, Jonathan Corbet wrote: > I've just spent rather more time than I would like figuring out why the PDF > builds fail and what was needed to fix it. The result is the following > patch series. It's a combination of little mistakes and fragility in the > whole PDF build tool chain. > > Mauro, Daniel: Do you want the last two? Or otherwise give me acks? I'd > like to send the set Linusward forthwith so that 4.12 can come out with > a working PDF build.
Only now stumbled over the full thread, but the drm patch is already queued up for at least 4.13 (Dave was out and all that). I guess we could try to cherry-pick through stable. Personally I don't care at all for PDF builds, the only thing we do in our autobuilder is html, same for me locally when building docs. That tends to keep working :-) Also, 0-day only tests the htmlbuild. Maybe you want to ping Fu and ask him to add the pdfdocs to his build targets? -Daniel > > In general, I'm dismayed by the fragility of the whole thing. I'm also a > little concerned that nobody except Jim complained about the problem. > Perhaps nobody really cares about PDF output anymore? In the absence of a > concerted effort on somebody's part, I predict that PDF building will be > broken much of the time. I have to wonder if it's worth it... > > Jonathan Corbet (5): > Docs: Include the Latex "ifthen" package > Docs: Remove redundant geometry package inclusion > Docs: fix table problems in ras.rst > Docs: Use kernel-figure in vidioc-g-selection.rst > DRM: Fix an incorrectly formatted table > > Documentation/admin-guide/ras.rst | 10 ++-- > Documentation/conf.py | 3 +- > .../media/uapi/v4l/vidioc-g-selection.rst | 4 +- > include/drm/bridge/dw_hdmi.h | 70 > +++++++++++----------- > 4 files changed, 43 insertions(+), 44 deletions(-) > > -- > 2.13.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
