From: Jonathan Corbet <corbet@lwn.net>
To: Masanari Iida <standby24x7@gmail.com>
Cc: Jim Davis <jim.epost@gmail.com>,
emmanuel.grumbach@intel.com, David Miller <davem@davemloft.net>,
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>,
netdev@vger.kernel.org, johannes.berg@intel.com
Subject: Re: make mandocs build failure with next-20150407
Date: Thu, 16 Apr 2015 09:43:50 +0200 [thread overview]
Message-ID: <20150416094350.2cf7e38b@lwn.net> (raw)
In-Reply-To: <CALLJCT3E7V9eZ_5-kFY1StQ4t6h73EuEyDc8wRpgm1fGJXNnAg@mail.gmail.com>
On Thu, 16 Apr 2015 08:33:15 +0900
Masanari Iida <standby24x7@gmail.com> wrote:
> On Wed, Apr 8, 2015 at 7:41 AM, Jim Davis <jim.epost@gmail.com> wrote:
> > DOCPROC Documentation/DocBook/80211.xml
> > Error(.//include/net/mac80211.h:329): Cannot parse enum!
> > Error(.//include/net/mac80211.h:367): Cannot parse enum!
> > Warning(.//include/net/mac80211.h:381): No description found for
> > parameter 'type'
> > --
>
> This error start to appear on Linus's tree.
> make xmldocs stops after this error.
> Then run it again, make xmldocs process rest of the files.
>
> Add TO: netdev and patch authors for reporting the issue.
It's the result of some incomplete changes in the wireless tree; I sent a
fix to Johannes that he applied a couple of days ago. Once that hits
mainline the problem should go away.
Thanks,
jon
prev parent reply other threads:[~2015-04-16 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+r1Zhh1iwe4go+hOUwzngTphyareAvbooyRARihJa8LwbqHKg@mail.gmail.com>
2015-04-15 23:33 ` make mandocs build failure with next-20150407 Masanari Iida
2015-04-16 7:43 ` Jonathan Corbet [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=20150416094350.2cf7e38b@lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=jim.epost@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=standby24x7@gmail.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).