Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Fix writing to GAttrib socket without POLLOUT event
Date: Tue, 7 Dec 2010 22:58:18 +0200	[thread overview]
Message-ID: <20101207205818.GB24045@jh-x301> (raw)
In-Reply-To: <1291400928-12114-1-git-send-email-vinicius.gomes@openbossa.org>

Hi Vinicius,

On Fri, Dec 03, 2010, Vinicius Costa Gomes wrote:
> If the GIOChannel is in the buffered state (the default) the watch
> function is called without receiving a POLLOUT from the socket. GLib
> adds a G_IO_OUT condition just because there is space in the GIOChannel
> internal buffer.
> 
> The solution is disabling the internal buffer, which in turn, makes the
> call of g_io_channel_flush() useless.
> ---
>  attrib/gattrib.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)

Pushed upstream. Thanks.

Johan

      reply	other threads:[~2010-12-07 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 18:28 [PATCH] Fix writing to GAttrib socket without POLLOUT event Vinicius Costa Gomes
2010-12-07 20:58 ` Johan Hedberg [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=20101207205818.GB24045@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox