From: Marco Porsch <marco@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
Ivan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>,
Mike Krinkin <krinkin.m.u@gmail.com>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCHv2 6/6] mac80211: mesh power save basics
Date: Fri, 18 Jan 2013 12:55:13 +0100 [thread overview]
Message-ID: <50F93821.1030905@cozybit.com> (raw)
In-Reply-To: <1358509959.5035.0.camel@jlt4.sipsolutions.net>
On 01/18/2013 12:52 PM, Johannes Berg wrote:
> On Thu, 2013-01-17 at 17:34 +0100, Marco Porsch wrote:
>> On 01/16/2013 11:14 PM, Johannes Berg wrote:
>>> On Mon, 2013-01-07 at 16:04 +0100, Marco Porsch wrote:
>>>
>>>> mode determines when non-peer mesh STA may send Probe Requests and Mesh Peering
>>>
>>> Please break lines to less than 72 characters, I personally prefer
>>> around 60 or so but I'll apply 72 too.
>>>
>>>> +static inline bool ieee80211_has_qos_mesh_ps(__le16 qc)
>>>> +{
>>>> + return (qc & cpu_to_le16(IEEE80211_QOS_CTL_MESH_PS_LEVEL)) != 0;
>>>
>>> bool means you don't need the !=0 and parentheses.
>>
>> Actually, then it pops the following warning:
>> CHECK net/mac80211/mesh_ps.c
>> include/linux/ieee80211.h:584:19: warning: incorrect type in return
>> expression (different base types)
>> include/linux/ieee80211.h:584:19: expected bool
>> include/linux/ieee80211.h:584:19: got restricted __le16
>>
>>
>> Other functions in that file have following style:
>> static inline int ieee80211_has_pm(__le16 fc)
>> {
>> return (fc & cpu_to_le16(IEEE80211_FCTL_PM)) != 0;
>> }
>>
>> What do you recommend?
>
> I'm clearly not quick enough for you, sorry. I guess we should keep it
> as is then, but I see you removed it entirely later? Anyway ... I just
> wasn't aware sparse would then complain, that's a bit stupid but hey.
Ah sorry. I just realized that
1) all the inlines in that file are about Frame Control and none copes
with QoS Control
2) I am the only one using QoS Mesh PM and in just a single occasion
So... SNIP =)
--Marco
next prev parent reply other threads:[~2013-01-18 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 15:04 [PATCHv2 0/6] mesh power save - basics Marco Porsch
2013-01-07 15:04 ` [PATCHv2 1/6] nl80211: add range checks to mesh parameters Marco Porsch
2013-01-07 18:47 ` Thomas Pedersen
2013-01-07 15:04 ` [PATCHv2 2/6] mac80211: update mesh peer link counter during userspace peering Marco Porsch
2013-01-07 18:47 ` Thomas Pedersen
2013-01-07 15:04 ` [PATCHv2 3/6] mac80211: move add_tim to subfunction Marco Porsch
2013-01-07 15:04 ` [PATCHv2 4/6] {cfg,nl,mac}80211: set beacon interval and DTIM period on mesh join Marco Porsch
2013-01-07 15:04 ` [PATCHv2 5/6] {cfg,nl}80211: mesh power mode primitives and userspace access Marco Porsch
2013-01-07 15:04 ` [PATCHv2 6/6] mac80211: mesh power save basics Marco Porsch
2013-01-16 22:14 ` Johannes Berg
2013-01-17 14:08 ` Marco Porsch
2013-01-17 16:34 ` Marco Porsch
2013-01-18 11:52 ` Johannes Berg
2013-01-18 11:55 ` Marco Porsch [this message]
2013-01-16 9:49 ` [PATCHv2 0/6] mesh power save - basics Marco Porsch
2013-01-16 11:32 ` Johannes Berg
2013-01-16 21:57 ` Johannes Berg
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=50F93821.1030905@cozybit.com \
--to=marco@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=ivan.bezyazychnyy@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=krinkin.m.u@gmail.com \
--cc=linux-wireless@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 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.