linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, abhishekpandit@chromium.org
Subject: RE: device: Allow devices to be marked as wake capable
Date: Mon, 22 Jun 2020 16:49:38 -0700 (PDT)	[thread overview]
Message-ID: <5ef14392.1c69fb81.453ce.1971@mx.google.com> (raw)
In-Reply-To: <20200622164003.BlueZ.v5.1.I3a6c238b09e1a0fad69e69cc2e6f4063af989b37@changeid>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]


This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
While we are preparing for reviewing the patches, we found the following
issue/warning.

Test Result:
checkbuild Failed

Outputs:
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
src/device.c:1347:6: error: no previous declaration for ‘device_get_wake_support’ [-Werror=missing-declarations]
 1347 | bool device_get_wake_support(struct btd_device *device)
      |      ^~~~~~~~~~~~~~~~~~~~~~~
src/device.c:1365:6: error: no previous declaration for ‘device_get_wake_allowed’ [-Werror=missing-declarations]
 1365 | bool device_get_wake_allowed(struct btd_device *device)
      |      ^~~~~~~~~~~~~~~~~~~~~~~
src/device.c: In function ‘btd_device_flags_changed’:
src/device.c:6713:6: error: unused variable ‘i’ [-Werror=unused-variable]
 6713 |  int i;
      |      ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9223: src/bluetoothd-device.o] Error 1
make: *** [Makefile:4010: all] Error 2



---
Regards,
Linux Bluetooth

  reply	other threads:[~2020-06-22 23:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 23:40 [BlueZ PATCH v5 0/6] device: Allow devices to be marked as wake capable Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 1/6] mgmt: Add mgmt op and events for device flags Abhishek Pandit-Subedi
2020-06-22 23:49   ` bluez.test.bot [this message]
2020-06-22 23:40 ` [BlueZ PATCH v5 2/6] monitor: Decode device flags mgmt ops and event Abhishek Pandit-Subedi
2020-06-22 23:47   ` [BlueZ,v5,2/6] " bluez.test.bot
2020-06-22 23:40 ` [BlueZ PATCH v5 3/6] device: Support marking a device with wake allowed Abhishek Pandit-Subedi
2020-06-22 23:47   ` [BlueZ,v5,3/6] " bluez.test.bot
2020-06-23  0:10   ` [BlueZ PATCH v5 3/6] " Luiz Augusto von Dentz
2020-06-24  3:53     ` Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 4/6] client: Display wake allowed property with info Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 5/6] doc/device-api: Add WakeAllowed Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 6/6] input: Make HID devices support wake Abhishek Pandit-Subedi
2020-06-29 23:02 [BlueZ PATCH v6 1/6] mgmt: Add mgmt op and events for device flags Abhishek Pandit-Subedi
2020-06-29 23:19 ` device: Allow devices to be marked as wake capable bluez.test.bot

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=5ef14392.1c69fb81.453ce.1971@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=abhishekpandit@chromium.org \
    --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).