From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: notify userspace of security level change
Date: Sun, 13 May 2012 03:22:24 -0300 [thread overview]
Message-ID: <20120513062224.GC15956@joana> (raw)
In-Reply-To: <1336849910-29064-1-git-send-email-gustavo@padovan.org>
Hi,
* Gustavo Padovan <gustavo@padovan.org> [2012-05-12 16:11:49 -0300]:
> When the userspace request a security level change it needs to be notified
> of when the change is complete.
> This patch make the socket non writable while the security request is
> ongoing. If it succeeds POLL_OUT is emitted, otherwise the channel is
> disconnected.
I just sent a second version of this patches that includes comments Johan made
in the last e-mail for better understanding of what the problem really is.
Gustavo
next prev parent reply other threads:[~2012-05-13 6:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 0:12 pull request: bluetooth 2012-05-04 Gustavo Padovan
2012-05-08 7:07 ` Gustavo Padovan
2012-05-11 20:16 ` Gustavo Padovan
2012-05-12 18:22 ` John W. Linville
2012-05-12 19:09 ` Gustavo Padovan
2012-05-12 19:11 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-12 19:11 ` [PATCH 2/2] Bluetooth: mgmt: Fix device_connected sending order Gustavo Padovan
2012-05-13 6:20 ` [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-13 6:22 ` Gustavo Padovan [this message]
2012-05-13 4:31 ` pull request: bluetooth 2012-05-04 Johan Hedberg
-- strict thread matches above, loose matches on Subject: below --
2012-05-04 1:59 [PATCH 1/2] Bluetooth: notify userspace of security level change Gustavo Padovan
2012-05-06 16:07 ` Marcel Holtmann
2012-05-07 5:13 ` Gustavo Padovan
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=20120513062224.GC15956@joana \
--to=gustavo@padovan.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).