From: "David S. Miller" <davem@davemloft.net>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6 1/2] Fix documentation build failure
Date: Mon, 14 Feb 2005 14:36:36 -0800 [thread overview]
Message-ID: <20050214143636.3c073df6.davem@davemloft.net> (raw)
In-Reply-To: <20050214200017.GA29201@sirius.home>
On Mon, 14 Feb 2005 23:00:17 +0300
Sergey Vlasov <vsu@altlinux.ru> wrote:
> In linux-2.6.11-rc4-bk2 building of the documentation (make htmldocs)
> fails on "DOCPROC Documentation/DocBook/kernel-api.sgml" because of
> these errors:
>
> Error(/home/vsu/src/linux-2.6.11-rc4-bk2/include/linux/skbuff.h:936): cannot understand prototype: '#ifndef CONFIG_HAVE_ARCH_DEV_ALLOC_SKB '
> Error(/home/vsu/src/linux-2.6.11-rc4-bk2/drivers/video/fbmem.c:1265): cannot understand prototype: 'const char *global_mode_option; '
I think the htmldoc parser should be fixed instead.
prev parent reply other threads:[~2005-02-14 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 20:00 [PATCH 2.6 1/2] Fix documentation build failure Sergey Vlasov
2005-02-14 22:36 ` David S. Miller [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=20050214143636.3c073df6.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=vsu@altlinux.ru \
/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).