All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Wireless <linux-wireless@vger.kernel.org>
Cc: Jouni Malinen <jouni@codeaurora.org>,
	Rohan Dutta <drohan@codeaurora.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 mac80211-next tree
Date: Tue, 10 Nov 2020 09:43:06 +0100	[thread overview]
Message-ID: <2aaaefd6cfda1928e5ea397850fa6fca01fb0642.camel@sipsolutions.net> (raw)
In-Reply-To: <20201109164342.1ff7d645@canb.auug.org.au>

On Mon, 2020-11-09 at 16:43 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the mac80211-next tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1014: WARNING: Unexpected indentation.
> Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1016: WARNING: Block quote ends without a blank line; unexpected unindent.
> Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1019: WARNING: Unexpected indentation.
> 
> Introduced by commit
> 
>   9f0ffa418483 ("cfg80211: Add support to configure SAE PWE value to drivers")

Thanks Stephen, fixing it now.

johannes


  reply	other threads:[~2020-11-10  8:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09  5:43 linux-next: build warning after merge of the mac80211-next tree Stephen Rothwell
2020-11-10  8:43 ` Johannes Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-13 10:33 Stephen Rothwell
2021-04-13 10:39 ` Grumbach, Emmanuel
2021-04-13 11:32   ` Johannes Berg
2018-05-09  4:56 Stephen Rothwell
2018-05-09  7:44 ` Johannes Berg
2018-05-11 12:20 ` Kalle Valo
2018-05-12  3:55   ` Stephen Rothwell
2018-05-12  3:55     ` Stephen Rothwell
2018-05-23 21:55   ` Arnd Bergmann
2018-05-23 21:55     ` Arnd Bergmann
2018-05-24  4:11     ` Kalle Valo
2018-05-24  8:51       ` Arnd Bergmann
2018-05-24  8:51         ` Arnd Bergmann
2018-05-24 10:08         ` Kalle Valo
2018-05-12  3:57 ` Stephen Rothwell

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=2aaaefd6cfda1928e5ea397850fa6fca01fb0642.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=drohan@codeaurora.org \
    --cc=jouni@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@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 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.