From: Denis Kenzior <denkenz@gmail.com>
To: eNV25 <env252525@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/2] client: fix spurious newlines in station show
Date: Wed, 2 Nov 2022 14:59:28 -0500 [thread overview]
Message-ID: <ffc95d8d-78c5-7baf-c5be-0ed35e36895e@gmail.com> (raw)
In-Reply-To: <20221102092156.71357-1-env252525@gmail.com>
Hi,
On 11/2/22 04:21, eNV25 wrote:
> This change removes duplicated calls to display_table_footer(), in
> station show.
>
> Before this change, the bug caused an extra newline to be output every
> time the table updated. This only occurred when the network was
> disconnected.
>
> $ iwctl
> [iwd]# station wlan0 show
>
> ---
> client/station.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
Can I get a proper full name please? I can't take this into the repo otherwise.
Regards,
-Denis
next prev parent reply other threads:[~2022-11-02 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 9:21 [PATCH 1/2] client: fix spurious newlines in station show eNV25
2022-11-02 9:21 ` [PATCH 2/2] gitignore: add .cache eNV25
2022-11-02 18:59 ` [PATCH 1/2] client: fix spurious newlines in station show James Prestwood
2022-11-02 19:59 ` Denis Kenzior [this message]
2022-11-02 20:13 ` eNV25
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=ffc95d8d-78c5-7baf-c5be-0ed35e36895e@gmail.com \
--to=denkenz@gmail.com \
--cc=env252525@gmail.com \
--cc=iwd@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).