From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] coex: coex agent implementation
Date: Fri, 30 Nov 2018 21:10:18 +0100 [thread overview]
Message-ID: <20181130201018.GA2704@amd> (raw)
In-Reply-To: <1543570976-20522-1-git-send-email-antara.borwankar@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]
Hi!
> + dbus_message_iter_init_append(reply, &iter);
> +
> + dbus_message_iter_open_container(&iter, DBUS_TYPE_ARRAY,
> + OFONO_PROPERTIES_ARRAY_SIGNATURE,
> + &dict);
> +
> + value = coex->bt_active;
> + ofono_dbus_dict_append(&dict, "BTActive",
> + DBUS_TYPE_BOOLEAN, &value);
> +
> + value = coex->wlan_active;
> + ofono_dbus_dict_append(&dict, "WLANActive",
> + DBUS_TYPE_BOOLEAN, &value);
> +
> + band = ofono_wlan_bw_to_string(coex->wlan_bw);
> + ofono_dbus_dict_append(&dict, "WLANBandwidth",
> + DBUS_TYPE_STRING, &band);
Something wrong with tabs here?
> + if (coex->bt_active != coex->pending_bt_active) {
> + coex->bt_active = coex->pending_bt_active;
> + ofono_dbus_signal_property_changed(conn, path,
> + OFONO_COEX_INTERFACE,
> + "BTActive",
> + DBUS_TYPE_BOOLEAN,
> + &(coex->bt_active));
> + }
Could probably be reformatted to fit on less lines.
> + g_at_result_iter_init(&iter, result);
> +
> + if (!g_at_result_iter_next(&iter, "+XNRTCWSW:"))
> + return;
> +
> + g_at_result_iter_next_number(&iter, &wlan.safe_rx_min);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_next_number(&iter, &wlan.safe_rx_max);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_next_number(&iter, &wlan.safe_tx_min);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_next_number(&iter, &wlan.safe_tx_max);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_skip_next(&iter);
> +
> + g_at_result_iter_next_number(&iter, &wlan.num_safe_vector);
Making every second line empty does not really help readability...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-11-30 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 9:42 [PATCH 2/3] coex: coex agent implementation Antara Borwankar
2018-11-30 20:10 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-03 9:20 Antara Borwankar
2018-12-05 20:50 ` Denis Kenzior
2018-12-05 20:57 ` Denis Kenzior
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=20181130201018.GA2704@amd \
--to=pavel@ucw.cz \
--cc=ofono@ofono.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