From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] sbc: Use __asm__ keyword
Date: Tue, 27 Sep 2011 11:23:56 +0300 [thread overview]
Message-ID: <20110927082356.GC3952@dell> (raw)
In-Reply-To: <1315294844-28020-1-git-send-email-luiz.dentz@gmail.com>
Hi,
On Tue, Sep 06, 2011, Luiz Augusto von Dentz wrote:
> From: Maarten Bosmans <mkbosmans@gmail.com>
>
> ---
> sbc/sbc_primitives_armv6.c | 4 ++--
> sbc/sbc_primitives_iwmmxt.c | 4 ++--
> sbc/sbc_primitives_mmx.c | 14 +++++++-------
> sbc/sbc_primitives_neon.c | 28 ++++++++++++++--------------
> 4 files changed, 25 insertions(+), 25 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2011-09-27 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 7:40 [PATCH BlueZ] sbc: Use __asm__ keyword Luiz Augusto von Dentz
2011-09-06 8:40 ` Siarhei Siamashka
2011-09-06 10:02 ` Maarten Bosmans
2011-09-06 11:33 ` Siarhei Siamashka
2011-09-27 8:23 ` Johan Hedberg [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=20110927082356.GC3952@dell \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).