Linux-Bluetooth Archive on
 help / color / Atom feed
From: Shawn Nock <>
Subject: Re: [PATCH BlueZ] shared/io-libevent2: Add support for libevent2 based IO handing
Date: Wed, 06 Feb 2019 11:00:58 -0500
Message-ID: <> (raw)
In-Reply-To: <>

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.


Shawn Nock
Engineer, Monadnock Systems Ltd.

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 15:30 Shawn Nock
2019-02-06 15:45 ` Marcel Holtmann
2019-02-06 16:00   ` Shawn Nock [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox