Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: make L2CAP sockets to inherit parent's priority
Date: Fri, 04 Nov 2011 22:06:35 +0100	[thread overview]
Message-ID: <1320440796.15441.299.camel@aeonflux> (raw)
In-Reply-To: <1320415430-2054-1-git-send-email-luiz.dentz@gmail.com>

Hi Luiz,

> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This makes priority set on a listen socket to be passed when accepting
> new connections.

I am in general fine with this, but is this the expected behavior of
SO_PRIORITY from other socket types?

Regards

Marcel



  parent reply	other threads:[~2011-11-04 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 14:03 [PATCH 1/2] Bluetooth: make L2CAP sockets to inherit parent's priority Luiz Augusto von Dentz
2011-11-04 14:03 ` [PATCH 2/2] Bluetooth: make RFCOMM " Luiz Augusto von Dentz
2011-11-04 21:06 ` Marcel Holtmann [this message]
2011-11-15  9:53   ` [PATCH 1/2] Bluetooth: make L2CAP " Luiz Augusto von Dentz

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=1320440796.15441.299.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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