public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bp1001 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] ac04e5: device: Fix not probing drivers at startup
Date: Wed, 09 Aug 2023 17:56:28 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/fc6f58-8bf3a4@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: ac04e5f38225d672a10ffd0a9162c3e466b6977b
      https://github.com/bluez/bluez/commit/ac04e5f38225d672a10ffd0a9162c3e466b6977b
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2023-08-09 (Wed, 09 Aug 2023)

  Changed paths:
    M src/device.c

  Log Message:
  -----------
  device: Fix not probing drivers at startup

Patch 67a26abe53bf ("profile: Add probe_on_discover flag") introduced a
regression which prevents drivers to be properly loaded at startup since
at that point they are not connected when code shall testing if
the devide is temporary instead.


  Commit: 8bf3a4a265bb199e21735639c57f1f652e5b8d45
      https://github.com/bluez/bluez/commit/8bf3a4a265bb199e21735639c57f1f652e5b8d45
  Author: Bart Philips <bartphilips1@gmail.com>
  Date:   2023-08-09 (Wed, 09 Aug 2023)

  Changed paths:
    M src/shared/gatt-server.c

  Log Message:
  -----------
  shared/gatt-server: Fix not allowing valid attribute writes

The length check shall not consider the command header, just its
payload.


Compare: https://github.com/bluez/bluez/compare/fc6f5856d177...8bf3a4a265bb

                 reply	other threads:[~2023-08-10  0:56 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/fc6f58-8bf3a4@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