[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10411162.7U3r8zC6Ku@pc-42>
Date: Fri, 21 Feb 2020 12:38:37 +0000
From: Jérôme Pouiller <Jerome.Pouiller@...abs.com>
To: Johannes Berg <johannes@...solutions.net>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jakub Kicinski <kuba@...nel.org>,
"David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH 09/10] cfg80211: align documentation style of
ieee80211_iface_combination
On Friday 21 February 2020 13:02:20 CET Johannes Berg wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Fri, 2020-02-21 at 12:56 +0100, Jerome Pouiller wrote:
> >
> > + * intervals:
> > + * * = 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.
>
> Hmm. I have a feeling I actually split this one out because
>
> > - * = 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.
--
Jérôme Pouiller
Powered by blists - more mailing lists