From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b71c53: configure.ac: check for stdio.h
Date: Tue, 04 Mar 2025 07:15:20 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/524fa2-9a32b6@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b71c5327926696223dba0d78f4c9fe36767d16ec
https://github.com/bluez/bluez/commit/b71c5327926696223dba0d78f4c9fe36767d16ec
Author: orbea <orbea@riseup.net>
Date: 2025-03-04 (Tue, 04 Mar 2025)
Changed paths:
M configure.ac
Log Message:
-----------
configure.ac: check for stdio.h
This fixes a configure failure for readline.h with slibtoolize which
depends on HAVE_STDIO_H being defined. With GNU libtoolize this check is
implicit and with slibtoolize it will fail instead.
error: unknown type name 'FILE'
Since bluez depends on stdio.h itself there is no reason to not check
for it explicitly.
Gentoo-Issue: https://bugs.gentoo.org/950467
Commit: 688f5ee80fca9ff06cdc1b1e51d4989e18147f1d
https://github.com/bluez/bluez/commit/688f5ee80fca9ff06cdc1b1e51d4989e18147f1d
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2025-03-04 (Tue, 04 Mar 2025)
Changed paths:
M client/bluetoothctl-admin.rst
M client/bluetoothctl-advertise.rst
M client/bluetoothctl-assistant.rst
M client/bluetoothctl-endpoint.rst
M client/bluetoothctl-gatt.rst
M client/bluetoothctl-hci.rst
M client/bluetoothctl-mgmt.rst
M client/bluetoothctl-monitor.rst
M client/bluetoothctl-player.rst
M client/bluetoothctl-scan.rst
M client/bluetoothctl-transport.rst
M doc/hci.rst
M doc/l2cap.rst
M doc/rfcomm.rst
M mesh/bluetooth-meshd.rst.in
M monitor/btmon.rst
M src/bluetoothd.rst.in
M tools/bdaddr.rst
M tools/btattach.rst
M tools/btmgmt.rst
M tools/ciptool.rst
M tools/hciattach.rst
M tools/hciconfig.rst
M tools/hcidump.rst
M tools/hcitool.rst
M tools/hid2hci.rst
M tools/isotest.rst
M tools/l2ping.rst
M tools/rctest.rst
M tools/rfcomm.rst
M tools/sdptool.rst
Log Message:
-----------
doc: Fix typo in the copyright header
Commit: 9a32b6144d8a9d7aedfa696e0aa8572c13c58480
https://github.com/bluez/bluez/commit/9a32b6144d8a9d7aedfa696e0aa8572c13c58480
Author: Amisha Jain <quic_amisjain@quicinc.com>
Date: 2025-03-04 (Tue, 04 Mar 2025)
Changed paths:
M obexd/plugins/mas.c
M obexd/plugins/messages-dummy.c
Log Message:
-----------
obex: Add messages_get_message() implementation for MAP plugin
GET Message() operation should be supported for passing below PTS
testcases -
1.MAP/MSE/MMB/BV-12-C
Verify that the MSE can return an email message to the MCE.
2.MAP/MSE/MMB/BV-13-C
Verify that the MSE can return a a*n* SMS message in native format
to the MCE.
3.MAP/MSE/MMB/BV-14-C
Verify that the MSE can return a SMS message with text trans-coded
to UTF-8 to the MCE.
Currently get message operation is not implemented, hence above
testcases are failing.
Added code to send the complete bmessage in response to the get() request
for the requested message handle.
As per suggested in previous patch, mmap() is being used
for reading file.
Compare: https://github.com/bluez/bluez/compare/524fa22ed19e...9a32b6144d8a
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-03-04 15:15 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/524fa2-9a32b6@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