All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org,
	Paulo Alcantara <paulo.alcantara@openbossa.org>
Subject: Re: [PATCH BlueZ] btio: Rescue lost errorneous numbers
Date: Tue, 24 Jul 2012 11:49:22 +0200	[thread overview]
Message-ID: <20120724094922.GB9576@x220.ice.intel.com> (raw)
In-Reply-To: <1343054163-19119-2-git-send-email-claudio.takahasi@openbossa.org>

Hi Claudio,

On Mon, Jul 23, 2012, Claudio Takahasi wrote:
> From: Paulo Alcantara <paulo.alcantara@openbossa.org>
> 
> The BT_IO_ERROR_* flags are not used for anything else and we just
> loosing errorneous numbers set in the sockets that might be more
> useful for handling specific errors.
> 
> A use case would be disconnect errors that should not allow BlueZ to
> enable auto connections since the connection would never be possible in
> some cases.
> 
> This patch removes BT_IO_ERROR_* flags and use the errors set in the
> sockets instead. Now, the errors passed in connect/disconnect callbacks
> should contain proper error numbers passed to them.
> ---
>  btio/btio.c |   78 ++++++++++++++++++++++++++++++++++++----------------------
>  btio/btio.h |    7 -----
>  2 files changed, 48 insertions(+), 37 deletions(-)

Applied. Thanks.

Johan

  parent reply	other threads:[~2012-07-24  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 14:36 [PATCH BlueZ] attio: Rename att_cleanup to attio_cleanup Claudio Takahasi
2012-07-23 14:36 ` [PATCH BlueZ] btio: Rescue lost errorneous numbers Claudio Takahasi
2012-07-23 16:16   ` Anderson Lizardo
2012-07-24  9:54     ` Johan Hedberg
2012-07-24 13:39       ` Claudio Takahasi
2012-07-24  9:49   ` Johan Hedberg [this message]
2012-07-24  9:49 ` [PATCH BlueZ] attio: Rename att_cleanup to attio_cleanup Johan Hedberg

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=20120724094922.GB9576@x220.ice.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=claudio.takahasi@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=paulo.alcantara@openbossa.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.