From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 6270ad: client: Fix build warning
Date: Tue, 05 Jul 2022 10:46:22 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/575778-e681fa@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 6270ad35b2f7b71dbc0a76b825f2f3ca07f936d2
https://github.com/bluez/bluez/commit/6270ad35b2f7b71dbc0a76b825f2f3ca07f936d2
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-07-05 (Tue, 05 Jul 2022)
Changed paths:
M client/player.c
Log Message:
-----------
client: Fix build warning
This fixes the following build warning:
warning: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead
[-Wdeprecated-declarations]
Commit: e681fae6bcceb73ebab16e6f8c4eabd6265dd40f
https://github.com/bluez/bluez/commit/e681fae6bcceb73ebab16e6f8c4eabd6265dd40f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-07-05 (Tue, 05 Jul 2022)
Changed paths:
M monitor/att.c
Log Message:
-----------
monitor: Fix build error in some targets
This fixes the following error:
monitor/att.c: In function 'print_attribute':
monitor/att.c:1850:35: error: lvalue required as unary '&' operand
print_uuid(label, &cpu_to_le16(uuid->value.u16), 2);
Compare: https://github.com/bluez/bluez/compare/575778a45f84...e681fae6bcce
reply other threads:[~2022-07-05 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/575778-e681fa@github.com \
--to=noreply@github.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).