From: Johannes Berg <johannes@sipsolutions.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-doc@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: nested structs parsing
Date: Thu, 29 Mar 2018 16:26:33 +0200 [thread overview]
Message-ID: <1522333593.24162.12.camel@sipsolutions.net> (raw)
In-Reply-To: <20180329112209.5c0e0320@vento.lan>
Hi,
> The original patchset for nested structs was supporting it only
> when not inlined. This should be fixed on this patchset:
>
> https://lkml.org/lkml/2018/2/19/387
>
> Do you have those patches on your tree?
No, looks like I don't have those yet. I'll wait for those then.
> With regards to duplicated warnings, that use to happen if the same header
> is included several times (with is a common pratice at the net subsystem).
Yeah, doesn't really matter anyway. I think I have to, in a sense,
because I'm getting lots of functions separately from the headers.
> Could you please merge from docs-next and see if those problems
> get solved?
No, that doesn't seem to address it fully:
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.packets' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.bytes' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.last_rate' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'msdu' not described in 'sta_info'
You can reproduce this in
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
(merging with docs-next) and running
make SPHINXDIRS=driver-api/80211 htmldocs
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-doc@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: nested structs parsing
Date: Thu, 29 Mar 2018 16:26:33 +0200 [thread overview]
Message-ID: <1522333593.24162.12.camel@sipsolutions.net> (raw)
In-Reply-To: <20180329112209.5c0e0320@vento.lan>
Hi,
> The original patchset for nested structs was supporting it only
> when not inlined. This should be fixed on this patchset:
>
> https://lkml.org/lkml/2018/2/19/387
>
> Do you have those patches on your tree?
No, looks like I don't have those yet. I'll wait for those then.
> With regards to duplicated warnings, that use to happen if the same header
> is included several times (with is a common pratice at the net subsystem).
Yeah, doesn't really matter anyway. I think I have to, in a sense,
because I'm getting lots of functions separately from the headers.
> Could you please merge from docs-next and see if those problems
> get solved?
No, that doesn't seem to address it fully:
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.packets' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.bytes' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'tx_stats.last_rate' not described in 'sta_info'
net/mac80211/sta_info.h:586: warning: Function parameter or member 'msdu' not described in 'sta_info'
You can reproduce this in
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
(merging with docs-next) and running
make SPHINXDIRS=driver-api/80211 htmldocs
johannes
next prev parent reply other threads:[~2018-03-29 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 9:46 nested structs parsing Johannes Berg
2018-03-29 9:46 ` Johannes Berg
2018-03-29 9:47 ` Johannes Berg
2018-03-29 9:47 ` Johannes Berg
2018-03-29 14:22 ` Mauro Carvalho Chehab
2018-03-29 14:22 ` Mauro Carvalho Chehab
2018-03-29 14:26 ` Johannes Berg [this message]
2018-03-29 14:26 ` Johannes Berg
2018-03-29 14:48 ` Mauro Carvalho Chehab
2018-03-29 14:48 ` Mauro Carvalho Chehab
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=1522333593.24162.12.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mchehab@s-opensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.