From: Johannes Berg <johannes@sipsolutions•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>, linux-wireless@vger•kernel.org
Cc: Carl Huang <cjhuang@codeaurora•org>,
David Miller <davem@davemloft•net>,
Networking <netdev@vger•kernel.org>,
Jakub Kicinski <kuba@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the origin tree
Date: Wed, 06 Jan 2021 23:23:42 +0100 [thread overview]
Message-ID: <220ccdfe5f7fad6483816cf470a506d250277a1a.camel@sipsolutions.net> (raw)
In-Reply-To: <20210107090550.725f9dc9@canb.auug.org.au> (sfid-20210106_230900_992127_37DD3A83)
Hi Stephen,
On Thu, 2021-01-07 at 09:05 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Building Linus' tree, today's linux-next build (htmldocs) produced
> this warning:
>
> include/net/mac80211.h:4200: warning: Function parameter or member 'set_sar_specs' not described in 'ieee80211_ops'
>
> Introduced by commit
>
> c534e093d865 ("mac80211: add ieee80211_set_sar_specs")
>
> Sorry, I missed this earlier.
Right, thanks. I believe I also fixed it in the patch I sent a few days
ago that fixed the other documentation warning related to SAR that you
reported.
Thanks,
johannes
next prev parent reply other threads:[~2021-01-06 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 22:05 linux-next: build warning after merge of the origin tree Stephen Rothwell
2021-01-06 22:23 ` Johannes Berg [this message]
2021-01-06 22:44 ` Stephen Rothwell
2021-01-06 22:46 ` Johannes Berg
2021-01-06 23:20 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 6:03 Stephen Rothwell
2025-01-22 10:00 ` Akira Yokosawa
2025-01-22 13:39 ` Bagas Sanjaya
2025-01-22 14:46 ` Akira Yokosawa
2025-01-23 0:27 ` Bagas Sanjaya
2025-01-22 21:57 ` Stephen Rothwell
2024-03-25 1:17 Stephen Rothwell
2022-01-17 0:45 Stephen Rothwell
2022-01-17 1:27 ` Suren Baghdasaryan
2022-01-17 2:24 ` Stephen Rothwell
2022-01-17 22:01 ` Andrew Morton
2019-11-27 20:59 Stephen Rothwell
2019-11-28 8:11 ` Linus Walleij
2012-05-14 0:44 Stephen Rothwell
2012-05-14 3:00 ` David Miller
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=220ccdfe5f7fad6483816cf470a506d250277a1a.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=cjhuang@codeaurora$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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