linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcid D-Bus patch(Error Messages)
Date: Thu, 29 Sep 2005 18:27:43 +0200	[thread overview]
Message-ID: <1128011263.30743.11.camel@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb05092805194782ba65@mail.gmail.com>

Hi Claudio,

> it's possible use uint32 without problems.
> 
> - 0x00000000 - 0x000000FF Bluetooth error codes (current situation)
> - 0x00000100 - 0x0000FFFF Reserved for future Bluetooth error codes
> extension
> - 0x00010000 - 0x0001FFFF D-Bus errors
> - 0x00020000 - 0x0003FFFF System errors (0x00020000 + system error
> value)
> - 0x00040000 - 0xFFFFFFFF Reserved to future error classes
> 
> In order to make easier discover the error type, I defined the error
> values range 
> considering bitwise operations.

this looks good to me. Any complaints or comments from others.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-09-29 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 14:27 [Bluez-devel] hcid D-Bus patch(Error Messages) Claudio Takahasi
2005-09-28  8:38 ` Marcel Holtmann
2005-09-28 12:19   ` Claudio Takahasi
2005-09-29 16:27     ` Marcel Holtmann [this message]

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=1128011263.30743.11.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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).