2015-04-07 22:41:30

by Jim Davis

[permalink] [raw]
Subject: make mandocs build failure with next-20150407

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'


2015-04-15 23:33:24

by Masanari Iida

[permalink] [raw]
Subject: Re: make mandocs build failure with next-20150407

On Wed, Apr 8, 2015 at 7:41 AM, Jim Davis <[email protected]> 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.

Masanari

> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

2015-04-16 07:44:09

by Jonathan Corbet

[permalink] [raw]
Subject: Re: make mandocs build failure with next-20150407

On Thu, 16 Apr 2015 08:33:15 +0900
Masanari Iida <[email protected]> wrote:

> On Wed, Apr 8, 2015 at 7:41 AM, Jim Davis <[email protected]> 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