All of lore.kernel.org
 help / color / mirror / Atom feed
From: z4pdy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] c92911: client: Avoid scan prompt when discovery is alread...
Date: Sat, 08 Aug 2026 12:22:45 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1142763/000000-c92911@github.com> (raw)

  Branch: refs/heads/1142763
  Home:   https://github.com/bluez/bluez
  Commit: c92911888f02409001eaa8df5022928137a4f913
      https://github.com/bluez/bluez/commit/c92911888f02409001eaa8df5022928137a4f913
  Author: z4pdy <z4pdyy@gmail.com>
  Date:   2026-08-08 (Sat, 08 Aug 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Avoid scan prompt when discovery is already active

Check the adapter's Discovering property before prompting the user
to start scanning. This avoids prompting to scan when discovery is
already in progress, which previously resulted
in an org.bluez.Error.InProgress error.



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-08-08 19:22 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/1142763/000000-c92911@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.