From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-wireless@vger.kernel.org,
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:46:45 +0100 [thread overview]
Message-ID: <5d8482756d40df615f908d7f24decdbb9ccb0ac3.camel@sipsolutions.net> (raw)
In-Reply-To: <20210107094414.607e884e@canb.auug.org.au>
Hi Stephen,
> > 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.
>
> I don't think so :-( I did a htmldocs build with your patch ([PATCH
> v2] cfg80211/mac80211: fix kernel-doc for SAR APIs) on top of Linus'
> tree and still got this warning. That patch did not touch
> include/net/mac80211.h ...
Umm, I don't know what to say. I even added "cfg80211/mac80211" to the
subject, but somehow lost the change to mac80211.h. Sorry about that :(
I'll get a v3 out.
johannes
next prev parent reply other threads:[~2021-01-06 22:47 UTC|newest]
Thread overview: 14+ 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
2021-01-06 22:44 ` Stephen Rothwell
2021-01-06 22:46 ` Johannes Berg [this message]
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 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=5d8482756d40df615f908d7f24decdbb9ccb0ac3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=cjhuang@codeaurora.org \
--cc=davem@davemloft.net \
--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 \
--cc=sfr@canb.auug.org.au \
/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 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).