All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Johannes Berg <johannes.berg@intel.com>, 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: linux-next: build warning after merge of the origin tree
Date: Thu, 7 Jan 2021 09:05:50 +1100	[thread overview]
Message-ID: <20210107090550.725f9dc9@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-01-06 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 22:05 Stephen Rothwell [this message]
2021-01-06 22:23 ` linux-next: build warning after merge of the origin tree Johannes Berg
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 --
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  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=20210107090550.725f9dc9@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cjhuang@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=johannes.berg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.