All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Sven Eckelmann <sven@narfation.org>, b.a.t.m.a.n@lists.open-mesh.org
Cc: Omer Efrat <omer.efrat@tandemg.com>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCH v2 3/5] batman: use BIT_ULL for NL80211_STA_INFO_* attribute types
Date: Thu, 14 Jun 2018 13:05:16 +0200	[thread overview]
Message-ID: <1528974316.26847.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1567584.jbsRn7ofiA@bentobox> (sfid-20180614_125324_149221_2D722F3B)

On Thu, 2018-06-14 at 12:53 +0200, Sven Eckelmann wrote:
> Hi,
> 
> here are the infos which were missing and which should be included in the 
> commit message
> 
> > > Since 'filled' member in station_info changed to u64
> 
> in commit 739960f128e5 ("cfg80211/nl80211: Add support for 
> NL80211_STA_INFO_RX_DURATION")

Yeah, which actually means this patch isn't needed?

BIT(NL80211_STA_INFO_EXPECTED_THROUGHPUT) is fine since
NL80211_STA_INFO_EXPECTED_THROUGHPUT is actually == 27.

johannes

  reply	other threads:[~2018-06-14 11:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14 10:12 [B.A.T.M.A.N.] [PATCH v2 3/5] batman: use BIT_ULL for NL80211_STA_INFO_* attribute types Omer Efrat
2018-06-14 10:12 ` Omer Efrat
2018-06-14 10:12 ` Omer Efrat
2018-06-14 10:40 ` [B.A.T.M.A.N.] " Sven Eckelmann
2018-06-14 10:40   ` Sven Eckelmann
2018-06-14 10:40   ` Sven Eckelmann
2018-06-14 10:53   ` [B.A.T.M.A.N.] " Sven Eckelmann
2018-06-14 10:53     ` Sven Eckelmann
2018-06-14 11:05     ` Johannes Berg [this message]
2018-06-14 11:20       ` [B.A.T.M.A.N.] " Sven Eckelmann
2018-06-14 11:20         ` Sven Eckelmann
2018-06-14 12:50         ` [B.A.T.M.A.N.] " Omer Efrat
2018-06-14 12:50           ` Omer Efrat

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=1528974316.26847.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=omer.efrat@tandemg.com \
    --cc=sven@narfation.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.