From: Johannes Berg <johannes@sipsolutions.net>
To: Omer Efrat <omer.efrat@tandemg.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, devel@driverdev.osuosl.org
Subject: Re: [B.A.T.M.A.N.] [PATCH v3 0/5] use BIT_ULL for NL80211_STA_INFO_* attribute types
Date: Sun, 17 Jun 2018 22:28:26 +0200 [thread overview]
Message-ID: <1529267306.3070.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1529229951-17730-1-git-send-email-omer.efrat@tandemg.com> (sfid-20180617_120607_305286_FD9A7637)
On Sun, 2018-06-17 at 13:05 +0300, Omer Efrat wrote:
>
> Note: The following patch series only does some code clean up.
> The previous versions mentioned a bug fix but it appears as a mix up
> with some local changes because NL80211_STA_INFO_TID_STATS value actually
> equals 31.
Interesting. Thanks for checking!
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Omer Efrat <omer.efrat@tandemg.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH v3 0/5] use BIT_ULL for NL80211_STA_INFO_* attribute types
Date: Sun, 17 Jun 2018 22:28:26 +0200 [thread overview]
Message-ID: <1529267306.3070.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1529229951-17730-1-git-send-email-omer.efrat@tandemg.com> (sfid-20180617_120607_305286_FD9A7637)
On Sun, 2018-06-17 at 13:05 +0300, Omer Efrat wrote:
>
> Note: The following patch series only does some code clean up.
> The previous versions mentioned a bug fix but it appears as a mix up
> with some local changes because NL80211_STA_INFO_TID_STATS value actually
> equals 31.
Interesting. Thanks for checking!
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Omer Efrat <omer.efrat-CtGflUZwD1xBDgjK7y7TUQ@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org
Subject: Re: [PATCH v3 0/5] use BIT_ULL for NL80211_STA_INFO_* attribute types
Date: Sun, 17 Jun 2018 22:28:26 +0200 [thread overview]
Message-ID: <1529267306.3070.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1529229951-17730-1-git-send-email-omer.efrat-CtGflUZwD1xBDgjK7y7TUQ@public.gmane.org> (sfid-20180617_120607_305286_FD9A7637)
On Sun, 2018-06-17 at 13:05 +0300, Omer Efrat wrote:
>
> Note: The following patch series only does some code clean up.
> The previous versions mentioned a bug fix but it appears as a mix up
> with some local changes because NL80211_STA_INFO_TID_STATS value actually
> equals 31.
Interesting. Thanks for checking!
johannes
next prev parent reply other threads:[~2018-06-17 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 10:05 [B.A.T.M.A.N.] [PATCH v3 0/5] use BIT_ULL for NL80211_STA_INFO_* attribute types Omer Efrat
2018-06-17 10:05 ` Omer Efrat
2018-06-17 20:28 ` Johannes Berg [this message]
2018-06-17 20:28 ` Johannes Berg
2018-06-17 20:28 ` 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=1529267306.3070.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omer.efrat@tandemg.com \
/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.