linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antoine Lassagne <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 3c062e: obex: forward nicer failure messages to dbus
Date: Fri, 24 Oct 2025 02:43:47 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1015404/000000-3c062e@github.com> (raw)

  Branch: refs/heads/1015404
  Home:   https://github.com/bluez/bluez
  Commit: 3c062ef43f1126bd0531abbb3c0f40ace9b9844b
      https://github.com/bluez/bluez/commit/3c062ef43f1126bd0531abbb3c0f40ace9b9844b
  Author: Antoine Lassagne <antoine.lassagne@canonical.com>
  Date:   2025-10-24 (Fri, 24 Oct 2025)

  Changed paths:
    M obexd/client/session.c
    M tools/parser/obex.c
    A tools/parser/opcodes.h

  Log Message:
  -----------
  obex: forward nicer failure messages to dbus

Without the fix, the following error would appear:
"OBEX Connect failed with 0x53"
After the fix, the error message becomes:
"OBEX Connect failed: Service Unavailable"



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

                 reply	other threads:[~2025-10-24  9: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/1015404/000000-3c062e@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).