From: Shawn Nock <shawn@monadnock.ca>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] shared/io-libevent2: Add support for libevent2 based IO handing
Date: Wed, 06 Feb 2019 11:00:58 -0500 [thread overview]
Message-ID: <87h8dgucsl.fsf@mobile.monadnock.ca> (raw)
In-Reply-To: <5B669D65-754A-4DA6-8ECD-2BD0797551A8@holtmann.org>
Marcel Holtmann writes:
> why?
I'm converting a sizable libevent codebase from HCI to the management
API. This makes integration with the existing event loop seemless
(almost, see io_set_context).
It may be useful for anyone wanting to use the managment api in
combination with libevent.
S
--
Shawn Nock
Engineer, Monadnock Systems Ltd.
prev parent reply other threads:[~2019-02-06 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 15:30 [PATCH BlueZ] shared/io-libevent2: Add support for libevent2 based IO handing Shawn Nock
2019-02-06 15:45 ` Marcel Holtmann
2019-02-06 16:00 ` Shawn Nock [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=87h8dgucsl.fsf@mobile.monadnock.ca \
--to=shawn@monadnock.ca \
--cc=linux-bluetooth@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).