From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: ERAMOTO Masaya <eramoto.masaya@jp.fujitsu.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] tools/obexctl: Fix display of size/time during transfer
Date: Mon, 4 Dec 2017 14:21:53 +0200 [thread overview]
Message-ID: <CABBYNZKgood+9Jcmu9RT5o2YfxS8e4BLDw5RXFMS20WKbs5jow@mail.gmail.com> (raw)
In-Reply-To: <bf9cb175-d8ae-6b6d-6a05-90b087ac4b49@jp.fujitsu.com>
Hi Eramoto,
On Wed, Nov 29, 2017 at 10:29 AM, ERAMOTO Masaya
<eramoto.masaya@jp.fujitsu.com> wrote:
> When obexctl is run after starting to transfer a file, the transferred
> size and the remaining time will be extreme values first as below:
>
> [NEW] Transfer /org/bluez/obex/server/session8/transfer6
> [CHG] Transfer /org/bluez/obex/server/session8/transfer6 Transferred: 1670741 (@1670KB/s 03:52)
> [CHG] Transfer /org/bluez/obex/server/session8/transfer6 Transferred: 1703502 (@32KB/s 197:14)
> [CHG] Transfer /org/bluez/obex/server/session8/transfer6 Transferred: 1736263 (@32KB/s 197:13)
> ---
> tools/obexctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/obexctl.c b/tools/obexctl.c
> index ece50f682..33ee180a3 100644
> --- a/tools/obexctl.c
> +++ b/tools/obexctl.c
> @@ -2319,7 +2319,7 @@ static void transfer_added(GDBusProxy *proxy)
>
> data = g_new0(struct transfer_data, 1);
>
> - if (g_dbus_proxy_get_property(proxy, "Transfered", &iter))
> + if (g_dbus_proxy_get_property(proxy, "Transferred", &iter))
> dbus_message_iter_get_basic(&iter, &data->transferred);
>
> if (g_dbus_proxy_get_property(proxy, "Size", &iter))
> --
> 2.14.1
Applied, thanks.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2017-12-04 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 8:29 [PATCH BlueZ] tools/obexctl: Fix display of size/time during transfer ERAMOTO Masaya
2017-12-04 12:21 ` Luiz Augusto von Dentz [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=CABBYNZKgood+9Jcmu9RT5o2YfxS8e4BLDw5RXFMS20WKbs5jow@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=eramoto.masaya@jp.fujitsu.com \
--cc=linux-bluetooth@vger.kernel.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 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).