* Re: doc warnings in *80211 [not found] ` <62b8bf6f739d1e6e0320864ed0660c9c52b767c4.camel@sipsolutions.net> @ 2022-10-04 14:26 ` Jakub Kicinski 2022-10-04 22:23 ` Akira Yokosawa 0 siblings, 1 reply; 2+ messages in thread From: Jakub Kicinski @ 2022-10-04 14:26 UTC (permalink / raw) To: Johannes Berg; +Cc: netdev@vger.kernel.org, linux-wireless, linux-doc On Tue, 04 Oct 2022 09:51:07 +0200 Johannes Berg wrote: > > doing basic sanity checks before submitting the net-next PR I spotted > > that we have these warnings when building documentation on net-next: > > > > Documentation/driver-api/80211/cfg80211:48: ./include/net/cfg80211.h:6960: WARNING: Duplicate C declaration, also defined at driver-api/80211/cfg80211:6924. > > Declaration is '.. c:function:: void cfg80211_rx_assoc_resp (struct net_device *dev, struct cfg80211_rx_assoc_resp *data)'. > > Hmm. That's interesting. I guess it cannot distinguish between the type > of identifier? > > struct cfg80211_rx_assoc_resp vs. cfg80211_rx_assoc_resp() > > Not sure what do about it - rename one of them? > > > Documentation/driver-api/80211/mac80211:109: ./include/net/mac80211.h:5046: WARNING: Duplicate C declaration, also defined at driver-api/80211/mac80211:1065. > > Declaration is '.. c:function:: void ieee80211_tx_status (struct ieee80211_hw *hw, struct sk_buff *skb)'. > > Same here actually! > > I don't think either of these is new. Thanks for checking! Adding linux-doc, but I presume Jon & co are aware if this is not new. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: doc warnings in *80211 2022-10-04 14:26 ` doc warnings in *80211 Jakub Kicinski @ 2022-10-04 22:23 ` Akira Yokosawa 0 siblings, 0 replies; 2+ messages in thread From: Akira Yokosawa @ 2022-10-04 22:23 UTC (permalink / raw) To: Jakub Kicinski, Johannes Berg; +Cc: linux-doc, linux-wireless, netdev Hi, On Date: Tue, 4 Oct 2022 07:26:46 -0700, Jakub Kicinski wrote: > On Tue, 04 Oct 2022 09:51:07 +0200 Johannes Berg wrote: >> > doing basic sanity checks before submitting the net-next PR I spotted >> > that we have these warnings when building documentation on net-next: >> > >> > Documentation/driver-api/80211/cfg80211:48: ./include/net/cfg80211.h:6960: WARNING: Duplicate C declaration, also defined at driver-api/80211/cfg80211:6924. >> > Declaration is '.. c:function:: void cfg80211_rx_assoc_resp (struct net_device *dev, struct cfg80211_rx_assoc_resp *data)'. >> >> Hmm. That's interesting. I guess it cannot distinguish between the type >> of identifier? >> >> struct cfg80211_rx_assoc_resp vs. cfg80211_rx_assoc_resp() >> >> Not sure what do about it - rename one of them? >> >> > Documentation/driver-api/80211/mac80211:109: ./include/net/mac80211.h:5046: WARNING: Duplicate C declaration, also defined at driver-api/80211/mac80211:1065. >> > Declaration is '.. c:function:: void ieee80211_tx_status (struct ieee80211_hw *hw, struct sk_buff *skb)'. >> >> Same here actually! >> >> I don't think either of these is new. > > Thanks for checking! > > Adding linux-doc, but I presume Jon & co are aware if this is not new. Yes, this is a known issue of Sphinx >=3.0, which prevents us to bump required version of Sphinx from 2.4.x. Link to a relevant mail from Mauro in the lore archive: https://lore.kernel.org/r/20220702122311.358c0219@sal.lan/ Note that the same warnings can be seen when a kernel-doc comment is included from multiple .rst files under Documentation/ by accident. Actually, Sphinx < 3.0 can not detect such true duplicates. As far as I see, this issue still remains in the latest version of Sphinx (5.2.3). HTH, Akira ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-10-04 22:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20221003191128.68bfc844@kernel.org>
[not found] ` <62b8bf6f739d1e6e0320864ed0660c9c52b767c4.camel@sipsolutions.net>
2022-10-04 14:26 ` doc warnings in *80211 Jakub Kicinski
2022-10-04 22:23 ` Akira Yokosawa
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).