From: Randy Dunlap <rdunlap@infradead.org>
To: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: make mandocs error with next-20140812
Date: Tue, 12 Aug 2014 10:14:22 -0700 [thread overview]
Message-ID: <53EA4B6E.9000500@infradead.org> (raw)
In-Reply-To: <CA+r1Zhip1SZww=sueoRJD=ZzekqLJjeY7O461wnFVRdsuz+eWg@mail.gmail.com>
On 08/12/14 10:12, Jim Davis wrote:
> docproc: .//drivers/gpu/drm/drm_stub.c: No such file or directory
> make[1]: *** [Documentation/DocBook/drm.xml] Error 1
> make: *** [mandocs] Error 2
> --
Known and patch has been submitted. I'll try to get it merged.
--
~Randy
prev parent reply other threads:[~2014-08-12 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 17:12 make mandocs error with next-20140812 Jim Davis
2014-08-12 17:14 ` Randy Dunlap [this message]
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=53EA4B6E.9000500@infradead.org \
--to=rdunlap@infradead.org \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).