lp:bluez

Created by VCS imports on 2011-01-12 and last modified on 2020-06-02
Get this branch:
bzr branch lp:bluez

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
Bluez Utilities
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://git.kernel.org/pub/scm/bluetooth/bluez.git.

The next import is scheduled to run in 3 hours.

Last successful import was 2 hours ago.

Import started 2 hours ago on alnitak and finished 2 hours ago taking 25 seconds — see the log
Import started 10 hours ago on alnitak and finished 10 hours ago taking 20 seconds — see the log
Import started 16 hours ago on alnitak and finished 16 hours ago taking 20 seconds — see the log
Import started 22 hours ago on alnitak and finished 22 hours ago taking 25 seconds — see the log
Import started on 2020-06-01 on alnitak and finished on 2020-06-01 taking 20 seconds — see the log
Import started on 2020-06-01 on alnitak and finished on 2020-06-01 taking 20 seconds — see the log
Import started on 2020-06-01 on alnitak and finished on 2020-06-01 taking 20 seconds — see the log
Import started on 2020-05-31 on alnitak and finished on 2020-05-31 taking 20 seconds — see the log
Import started on 2020-05-31 on alnitak and finished on 2020-05-31 taking 20 seconds — see the log
Import started on 2020-05-31 on alnitak and finished on 2020-05-31 taking 20 seconds — see the log

Whiteboard

NOTE: Upstream imports have moved. They are done (by hand for now) here:
https://git.launchpad.net/~bluetooth/bluez?h=master

Recent revisions

20605. By MichaƂ Lowas-Rzechonek 3 hours ago

mesh: Fix FPE in overcommit logic.

During overcommit, mesh_config_save is called in asynchronous mode to
avoid blocking Send() calls. This means that update of cfg->write_time
is scheduled via l_idle_oneshot, so if the next Send() gets scheduled
first, the code may see elapsed time of zero.

If this happens, then the overcommit logic was already executed and the
overcommit is pending, so we can just return.

20604. By Inga Stotland <email address hidden> on 2020-06-01

mesh: Remove unused functions from net.c

The folllowing functionsa are not being used anywhere in the code and
have been removed:
mesh_net_flush()
mesh_net_prov_caps_get()
mesh_net_priv_key_get()
mesh_net_priv_key_set()
mesh_net_prov_rand()
mesh_net_prov_uni()
mesh_net_id_uuid_set()
mesh_net_test_addr()
mesh_net_test_mode()
mesh_net_uni_range_set()
mesh_net_uni_range_get()
mesh_net_set_window_accuracy()

20603. By Inga Stotland <email address hidden> on 2020-06-01

mesh: Clean up style in net.c

20602. By Inga Stotland <email address hidden> on 2020-06-01

mesh: Remove debug-only related callback for packet send

This removes callback for sending every single access layer packet
since the callback does nothing but print debug satement. This
functionality is mature enough not to require such heavy debugging.

20601. By Inga Stotland <email address hidden> on 2020-06-01

mesh: Debug output clean up

This changes l_info() to l_debug() for recurring cases and
removes some excessive debug output.

20600. By Inga Stotland <email address hidden> on 2020-06-01

mesh: Helper packet print should depend on debug setting

This changes the utility function print_packet() to check if
daemon is running in debug mode.

20599. By Alain Michaud <email address hidden> on 2020-06-01

a2dp: Fix double free in load_remote_sep

This patch fixes a double free condition in load_remote_sep. Value is
freed, then the inner loop is broken, but the rest of the outer loop
will attempt to free value again.

20598. By Sonny Sasaka <email address hidden> on 2020-06-01

a2dp: Fix ref counting bug of setup_unref

In a2dp_reconfig, setup is ref-counted by cb_data. However, in the fail
label setup is unref-ed but cb_data is not cleared. This may cause
double unref in the future if cb_data gets executed. Instead, we should
do setup_cb_free to clear cb_data and unref setup.

20597. By Luiz Augusto von Dentz <email address hidden> on 2020-05-28

adapter: Fix not removing client from discovery list

If command MGMT_OP_START_DISCOVERY fails we reply with btd_error_busy
but we don't remove the client from the list which would prevent the
client to start it once again.

20596. By Luiz Augusto von Dentz <email address hidden> on 2020-05-28

avrcp: Don't attempt to load settings if on volume changed is supported

If only volume changed is supported that means the player cannot really
indicate track/metadata changes so don't attempt to read them.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers