linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: frederic.dalleau@linux.intel.com
Cc: Michael Knudsen <m.knudsen@samsung.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] Bluetooth: Add BT_DEFER_SETUP option to sco socket
Date: Wed, 14 Nov 2012 23:39:47 +0900	[thread overview]
Message-ID: <1352903987.20338.8.camel@aeonflux> (raw)
In-Reply-To: <50A36E06.2060206@linux.intel.com>

Hi Fred,

> > My idea is to define (I'm not sure if this is exactly the same as what you
> > suggested yourself) a bit, LM_DEFER, that e.g. sco_connect_ind() may return
> > and propagate this bit to hci_conn_request_evt().  This way all policing of
> > accepting SCO connections is handled from a single entry point into sco.c.
> 
> You detailed it much further than I did, but yes it is the same idea. I 
> fully support it! If everybody agrees, then I can update the patch.
> 
> hci.h would receive the folowing line:
> 
> + #define HCI_LM_DEFER   0x4000

can we actually not that that. This is an old public API and I rather
not extend it.

Regards

Marcel



  reply	other threads:[~2012-11-14 14:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 18:20 [RFC] sco: BT_DEFER_SETUP for SCO sockets Frédéric Dalleau
2012-11-13 18:20 ` [RFC] Bluetooth: Add BT_DEFER_SETUP option to sco socket Frédéric Dalleau
2012-11-13 18:45   ` Luiz Augusto von Dentz
2012-11-14  8:26   ` Michael Knudsen
2012-11-14 10:10     ` Frédéric Dalleau
2012-11-14 14:39       ` Marcel Holtmann [this message]
2012-11-14  9:17   ` Andrei Emeltchenko
2012-11-14 10:09   ` Arnaud Mouiche
2012-11-14 10:18     ` Frédéric Dalleau
2012-11-14 10:33       ` Arnaud Mouiche
2012-11-14 10:21     ` Michael Knudsen
2012-11-15 20:30   ` Gustavo Padovan
2012-11-16 12:10     ` Frédéric Dalleau

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=1352903987.20338.8.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=frederic.dalleau@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=m.knudsen@samsung.com \
    /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).