From: Johannes Berg <johannes@sipsolutions.net>
To: "Jérôme Pouiller" <Jerome.Pouiller@silabs.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH 09/10] cfg80211: align documentation style of ieee80211_iface_combination
Date: Fri, 21 Feb 2020 13:41:24 +0100 [thread overview]
Message-ID: <1cbc48003d249d3ce14941adbb32089b57573cd0.camel@sipsolutions.net> (raw)
In-Reply-To: <10411162.7U3r8zC6Ku@pc-42>
On Fri, 2020-02-21 at 12:38 +0000, Jérôme Pouiller wrote:
>
> > > - * = 0
> > > - * all beacon intervals for different interface must be same.
> > > - * > 0
> > > - * any beacon interval for the interface part of this combination AND
> > > - * GCD of all beacon intervals from beaconing interfaces of this
> > > - * combination must be greater or equal to this value.
> >
> > This generates the nicer output, not with bullets but as a definition
> > list or something.
> Indeed.
>
> Unfortunately, I hasn't been able to use the same syntax in struct
> description: if sphinx find a blank line, it considers that the rest of
> the input is the long description of the struct.
So let's just leave it as is. I don't consider using the same style
(inline or header) everywhere to be even nearly as important as the
output :)
johannes
next prev parent reply other threads:[~2020-02-21 12:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:55 [PATCH 01/10] cfg80211: drop duplicated documentation of field "probe_resp_offload" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 02/10] cfg80211: drop duplicated documentation of field "privid" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 03/10] cfg80211: drop duplicated documentation of field "registered" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 04/10] cfg80211: drop duplicated documentation of field "_net" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 05/10] cfg80211: drop duplicated documentation of field "perm_addr" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 06/10] cfg80211: drop duplicated documentation of field "reg_notifier" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 07/10] cfg80211: merge documentations of field "debugfsdir" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 08/10] cfg80211: merge documentations of field "dev" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 09/10] cfg80211: align documentation style of ieee80211_iface_combination Jerome Pouiller
2020-02-21 12:02 ` Johannes Berg
2020-02-21 12:38 ` Jérôme Pouiller
2020-02-21 12:41 ` Johannes Berg [this message]
2020-02-21 12:49 ` Jérôme Pouiller
2020-02-21 11:56 ` [PATCH 10/10] cfg80211: fix indentation errors Jerome Pouiller
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=1cbc48003d249d3ce14941adbb32089b57573cd0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Jerome.Pouiller@silabs.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@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 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).