Closed Bug 1179141 Opened 9 years ago Closed 9 years ago

[cleanup] Remove macro |BT_API2_LOGR|

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(firefox42 fixed)

RESOLVED FIXED
FxOS-S2 (10Jul)
Tracking Status
firefox42 --- fixed

People

(Reporter: ben.tian, Assigned: ben.tian)

References

Details

Attachments

(1 file, 1 obsolete file)

Remove macro |BT_API2_LOGR| as we already switched to bluetooth2 on m-c.
Also remove redundant logs.
Assignee: nobody → btian
Attachment #8628135 - Flags: review?(joliu)
Comment on attachment 8628135 [details] [diff] [review]
Patch 1 (v1): Remove macro |BT_API2_LOGR|

Review of attachment 8628135 [details] [diff] [review]:
-----------------------------------------------------------------

r=me after comments addressed, thanks for the cleanup.

::: dom/bluetooth/bluedroid/BluetoothGattManager.cpp
@@ +1354,5 @@
>  BluetoothGattManager::RegisterClientNotification(BluetoothGattStatus aStatus,
>                                                   int aClientIf,
>                                                   const BluetoothUuid& aAppUuid)
>  {
> +  BT_LOGR("Client Registered, clientIf = %d", aClientIf);

I think it can be removed, since we can see the similar log by enabling stack log.

@@ +1370,5 @@
>    NS_ENSURE_TRUE_VOID(bs);
>  
>    if (aStatus != GATT_STATUS_SUCCESS) {
> +    BT_LOGR("RegisterClient failed, clientIf = %d, status = %d, appUuid = %s",
> +            aClientIf, aStatus, NS_ConvertUTF16toUTF8(uuid).get());

nit: How about using BT_LOGD for these failed operations?

@@ +1448,5 @@
>                                            BluetoothGattStatus aStatus,
>                                            int aClientIf,
>                                            const nsAString& aDeviceAddr)
>  {
> +  BT_LOGR();

I think it's redundant, what do you think?

@@ +1462,5 @@
>    nsRefPtr<BluetoothGattClient> client = sClients->ElementAt(index);
>  
>    if (aStatus != GATT_STATUS_SUCCESS) {
> +    BT_LOGR("Connect failed, clientIf = %d, connId = %d, status = %d",
> +            aClientIf, aConnId, aStatus);

DITTO.

@@ +1501,5 @@
>                                               BluetoothGattStatus aStatus,
>                                               int aClientIf,
>                                               const nsAString& aDeviceAddr)
>  {
> +  BT_LOGR();

DITTO.

@@ +2028,5 @@
>                                                   const nsAString& aBdAddr,
>                                                   int aRssi,
>                                                   BluetoothGattStatus aStatus)
>  {
> +  BT_LOGR();

DITTO.

@@ +2043,5 @@
>  
>    if (aStatus != GATT_STATUS_SUCCESS) { // operation failed
> +    BT_LOGR("ReadRemoteRssi failed, clientIf = %d, bdAddr = %s, rssi = %d, " \
> +            "status = %d", aClientIf, NS_ConvertUTF16toUTF8(aBdAddr).get(),
> +            aRssi, (int)aStatus);

DITTO.

::: dom/bluetooth/bluetooth2/BluetoothReplyRunnable.cpp
@@ +24,5 @@
>    , mErrorStatus(STATUS_FAIL)
>    , mName(aName)
>  {
>    if (aPromise) {
> +    BT_LOGR("<%s>", NS_ConvertUTF16toUTF8(mName).get());

Do we need to have these logs here and below?
I would suggest to remove them since they looked a bit of redundant to me.
Attachment #8628135 - Flags: review?(joliu) → review+
Revise based on reviewer's comment.
Attachment #8628135 - Attachment is obsolete: true
Blocks: 1179682
https://hg.mozilla.org/mozilla-central/rev/2c12938d0840
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S2 (10Jul)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: