From: Arkadiusz Bokowy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 12d7c4: lib: Add missing includes in bluetooth/hci.h
Date: Mon, 25 Aug 2025 11:43:33 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/995364/000000-95b108@github.com> (raw)
Branch: refs/heads/995364
Home: https://github.com/bluez/bluez
Commit: 12d7c41fa726fe800c84b92efe87901dbaefa04c
https://github.com/bluez/bluez/commit/12d7c41fa726fe800c84b92efe87901dbaefa04c
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2025-08-25 (Mon, 25 Aug 2025)
Changed paths:
M lib/bluetooth/hci.h
Log Message:
-----------
lib: Add missing includes in bluetooth/hci.h
Compilation fails when using bluetooth/hci.h without other includes.
> /usr/include/bluetooth/hci.h:310:9: error: unknown type name ‘uint8_t’
> 310 | uint8_t lap[3];
> | ^~~~~~~
> ...
> /usr/include/bluetooth/hci.h:383:9: error: unknown type name ‘bdaddr_t’; did you mean ‘daddr_t’?
> 383 | bdaddr_t bdaddr;
> | ^~~~~~~~
> ...
Commit: 95b1086bb07bf75682e4e5f65dbd81700e7f4ccf
https://github.com/bluez/bluez/commit/95b1086bb07bf75682e4e5f65dbd81700e7f4ccf
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2025-08-25 (Mon, 25 Aug 2025)
Changed paths:
M lib/bluetooth/hci_lib.h
Log Message:
-----------
lib: Add missing includes in bluetooth/hci_lib.h
Compilation fails when using bluetooth/hci_lib.h without other includes.
> /usr/include/bluetooth/hci_lib.h:21:9: error: unknown type name ‘uint16_t’
> 21 | uint16_t ogf;
> | ^~~~~~~~
> ...
> /usr/include/bluetooth/hci_lib.h:182:27: error: ‘HCI_VENDOR_PKT’ undeclared
> 182 | hci_set_bit((t == HCI_VENDOR_PKT) ? 0 : (t & HCI_FLT_TYPE_BITS), &f->type_mask);
> | ^~~~~~~~~~~~~~
Compare: https://github.com/bluez/bluez/compare/12d7c41fa726%5E...95b1086bb07b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-08-25 18:43 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/995364/000000-95b108@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).