From: Denis Kenzior <denkenz@gmail.com>
To: Michael Johnson <mjohnson459@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2] netdev: Add logging for CQM messages
Date: Tue, 2 Aug 2022 11:11:57 -0500 [thread overview]
Message-ID: <ab74cfbd-251f-a77b-e46c-b2c97c737674@gmail.com> (raw)
In-Reply-To: <20220802104728.48628-1-mjohnson459@gmail.com>
Hi Michael,
On 8/2/22 05:47, Michael Johnson wrote:
> Add extra logging around CQM events to help track wifi status. This is
> useful for headless systems that can only be accessed over the network
> and so information in the logs is invaluable for debugging outages.
>
> Prior to this change, the only log for CQM messages is saying one was
> received. This adds details to what attributes were set and the
> associated data with them.
>
> The signal strength log format was chosen to roughly match
> wpa_supplicant's which looks like this:
>
> CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=-96 txrate=6000
> ---
> src/netdev.c | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2022-08-02 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 10:47 [PATCH v2] netdev: Add logging for CQM messages Michael Johnson
2022-08-02 16:11 ` Denis Kenzior [this message]
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=ab74cfbd-251f-a77b-e46c-b2c97c737674@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=mjohnson459@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox