From: Szymon Janc <szymon.janc@tieto.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 4/4] emulator: Fix crash if socket(AF_ALG) is not supported by the kernel
Date: Mon, 27 Jan 2014 21:52:52 +0100 [thread overview]
Message-ID: <57954003.qHnYYJdjKE@leonov> (raw)
In-Reply-To: <CAJdJm_MHvakZpy_j_X3ACOS9EegKyO8WKL45w5u4t_h2LOBXww@mail.gmail.com>
Hi,
On Monday 27 of January 2014 16:03:59 Anderson Lizardo wrote:
> Hi Johan,
>
> On Mon, Jan 27, 2014 at 1:59 PM, Johan Hedberg <johan.hedberg@gmail.com>
wrote:
> > This patch has been applied. Thanks.
>
> Any comments on the other patches that touch android/* files?
Applied as well, thanks.
--
BR
Szymon Janc
prev parent reply other threads:[~2014-01-27 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 21:24 [PATCH BlueZ 0/4] android: Minor fixes Anderson Lizardo
2014-01-23 21:24 ` [PATCH BlueZ 1/4] android/tester: Fix crash on failure inside setup() Anderson Lizardo
2014-01-23 21:24 ` [PATCH BlueZ 2/4] android: Remove useless extra parenthesis Anderson Lizardo
2014-01-23 21:24 ` [PATCH BlueZ 3/4] android: Trivial replacement of tabs where spaces are expected Anderson Lizardo
2014-01-23 21:24 ` [PATCH BlueZ 4/4] emulator: Fix crash if socket(AF_ALG) is not support by the kernel Anderson Lizardo
2014-01-26 1:43 ` [PATCH BlueZ v2 0/4] android: Minor fixes Anderson Lizardo
2014-01-26 1:43 ` [PATCH BlueZ 1/4] android/tester: Fix crash on failure inside setup() Anderson Lizardo
2014-01-26 1:44 ` [PATCH BlueZ 2/4] android: Remove useless extra parenthesis Anderson Lizardo
2014-01-26 1:44 ` [PATCH BlueZ 3/4] android: Trivial replacement of tabs where spaces are expected Anderson Lizardo
2014-01-26 1:44 ` [PATCH BlueZ 4/4] emulator: Fix crash if socket(AF_ALG) is not supported by the kernel Anderson Lizardo
2014-01-27 17:59 ` Johan Hedberg
2014-01-27 20:03 ` Anderson Lizardo
2014-01-27 20:52 ` Szymon Janc [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=57954003.qHnYYJdjKE@leonov \
--to=szymon.janc@tieto.com \
--cc=anderson.lizardo@openbossa.org \
--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