linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Shawn Nock <shawn@monadnock.ca>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] shared/io-libevent2: Add support for libevent2 based IO handing
Date: Wed, 6 Feb 2019 16:45:57 +0100	[thread overview]
Message-ID: <5B669D65-754A-4DA6-8ECD-2BD0797551A8@holtmann.org> (raw)
In-Reply-To: <20190206153045.14788-1-shawn@monadnock.ca>

Hi Shawn,

> ---
> src/shared/io-libevent2.c | 247 ++++++++++++++++++++++++++++++++++++++
> src/shared/io.h           |   1 +
> 2 files changed, 248 insertions(+)
> create mode 100644 src/shared/io-libevent2.c

why?

Regards

Marcel


  reply	other threads:[~2019-02-06 15:46 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 [this message]
2019-02-06 16:00   ` Shawn Nock

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=5B669D65-754A-4DA6-8ECD-2BD0797551A8@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=shawn@monadnock.ca \
    /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).