From: Kalle Valo <kvalo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@nbd.name>,
Johannes Berg <johannes.berg@intel.com>,
Ryder Lee <ryder.lee@mediatek.com>,
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 wireless-next tree
Date: Fri, 31 Mar 2023 14:10:10 +0300 [thread overview]
Message-ID: <87y1ndb2i5.fsf@kernel.org> (raw)
In-Reply-To: <20230323141548.659479ef@canb.auug.org.au> (Stephen Rothwell's message of "Thu, 23 Mar 2023 14:15:48 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> After merging the wireless-next tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/driver-api/80211/mac80211-advanced:214:
> /home/sfr/next/next/net/mac80211/sta_info.h:628: ERROR: Unexpected
> indentation.
>
> Introduced by commit
>
> fe4a6d2db3ba ("wifi: mac80211: implement support for yet another
> mesh A-MSDU format")
Thanks, this commit should fix it:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=f102424befd3751386f3e2f2c70c5a1948248622
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-03-31 11:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 3:15 linux-next: build warning after merge of the wireless-next tree Stephen Rothwell
2023-03-31 11:10 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 3:29 Stephen Rothwell
2024-02-09 7:06 ` Johannes Berg
2023-09-14 2:49 Stephen Rothwell
2023-09-12 5:10 Stephen Rothwell
2023-02-15 4:20 Stephen Rothwell
2023-02-15 4:17 Stephen Rothwell
2023-01-19 5:24 Stephen Rothwell
2022-06-21 10:02 Stephen Rothwell
2022-05-17 10:00 Stephen Rothwell
2022-05-18 4:51 ` Kalle Valo
2014-09-30 8:46 Stephen Rothwell
2014-09-30 14:41 ` Larry Finger
2013-04-05 5:46 Stephen Rothwell
2013-04-04 1:00 Stephen Rothwell
2013-04-04 1:04 ` Stephen Rothwell
2013-04-04 1:17 ` Larry Finger
2013-04-04 2:36 ` Stephen Rothwell
2013-04-04 2:58 ` Larry Finger
2011-11-22 3:25 Stephen Rothwell
2011-11-22 7:56 ` Stanislaw Gruszka
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=87y1ndb2i5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--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 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.