From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] cb1a3f: shared/vcp: Fix build error
Date: Fri, 01 Dec 2023 10:21:45 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/4db4d5-cb1a3f@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: cb1a3fd96c48a878f1a93ffc81e0c5d867b03cd8
https://github.com/bluez/bluez/commit/cb1a3fd96c48a878f1a93ffc81e0c5d867b03cd8
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-11-30 (Thu, 30 Nov 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp: Fix build error
This fixes the following build error in some architectures:
src/shared/vcp.c:961:24: error: lvalue required as unary ‘&’ operand
961 | iov.iov_base = &cpu_to_le32(vocs->vocs_audio_loc);
| ^
reply other threads:[~2023-12-01 18:21 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/4db4d5-cb1a3f@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).