From: Sam Ravnborg <sam@ravnborg.org>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, randy.dunlap@oracle.com,
akpm@linux-foundation.org, jirislaby@gmail.com
Subject: Re: [Patch] kbuild: fix a build error during make htmldocs
Date: Sat, 20 Jun 2009 13:32:09 +0200 [thread overview]
Message-ID: <20090620113209.GA31560@uranus.ravnborg.org> (raw)
In-Reply-To: <20090619070909.6422.28484.sendpatchset@localhost.localdomain>
On Fri, Jun 19, 2009 at 03:06:54AM -0400, Amerigo Wang wrote:
>
> Fix the following build error when do 'make htmldocs':
>
> DOCPROC Documentation/DocBook/debugobjects.xml
> exec /scripts/kernel-doc: No such file or directory
> exec /scripts/kernel-doc: No such file or directory
>
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: WANG Cong <amwang@redhat.com>
> Cc: Sam <sam@ravnborg.org>
> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Applied, thanks Wang.
Sam
prev parent reply other threads:[~2009-06-20 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 7:06 [Patch] kbuild: fix a build error during make htmldocs Amerigo Wang
2009-06-20 11:32 ` Sam Ravnborg [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=20090620113209.GA31560@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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