From: "Alvin Šipraga" <alvin@pqrs.dk>
To: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-hsien Lin <chi-hsien.lin@infineon.com>,
Wright Feng <wright.feng@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"SHA-cyfmac-dev-list@infineon.com"
<SHA-cyfmac-dev-list@infineon.com>
Subject: Re: [PATCH 1/2] brcmfmac: fix setting of station info chains bitmask
Date: Mon, 14 Jun 2021 15:21:57 +0200 [thread overview]
Message-ID: <ea5a0ce5-1bc9-774c-06be-6ecc284531c5@pqrs.dk> (raw)
In-Reply-To: <20210506132010.3964484-1-alsi@bang-olufsen.dk>
Hello,
On 5/6/21 3:20 PM, Alvin Šipraga wrote:
> The sinfo->chains field is a bitmask for filled values in chain_signal
> and chain_signal_avg, not a count. Treat it as such so that the driver
> can properly report per-chain RSSI information.
>
<snip>
This is a gentle ping to see if these two patches got lost. I was told
on another mailing list recently that mail sent from my work address is
finding its way into peoples' junk folders.
I will resend the patches in the near future if I don't see any response
here.
Thanks,
Alvin
next prev parent reply other threads:[~2021-06-14 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 13:20 [PATCH 1/2] brcmfmac: fix setting of station info chains bitmask Alvin Šipraga
2021-05-06 13:20 ` [PATCH 2/2] brcmfmac: correctly report average RSSI in station info Alvin Šipraga
2021-06-14 13:21 ` Alvin Šipraga [this message]
2021-06-14 14:33 ` [PATCH 1/2] brcmfmac: fix setting of station info chains bitmask Kalle Valo
2021-06-14 17:18 ` Alvin Šipraga
2021-06-15 10:36 ` [1/2] " Kalle Valo
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=ea5a0ce5-1bc9-774c-06be-6ecc284531c5@pqrs.dk \
--to=alvin@pqrs.dk \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@infineon.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.