linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: "Yao, Costa" <cqyao@qca.qualcomm.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	qca-linux-team <qca-linux-team@qualcomm.com>
Subject: Re: [PATCH] ar3k: add patch and sysconfig for QCA9564(Aphrodite)
Date: Wed, 16 May 2012 23:39:04 +0100	[thread overview]
Message-ID: <1337207944.4107.57.camel@deadeye> (raw)
In-Reply-To: <07BBB2AAB1A10A488A2AD166C7CB8B0DF71079@nasanexd02b.na.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

On Thu, 2012-04-26 at 06:49 +0000, Yao, Costa wrote:
> From 8996c5715384d8f4dc40df4ad9b7686ddc654847 Mon Sep 17 00:00:00 2001
> From: Costa Yao <cqyao@qca.qualcomm.com>
> Date: Thu, 26 Apr 2012 14:38:06 +0800
> Subject: [PATCH] ar3k: add patch and sysconfig for QCA9564(Aphrodite)
> 
> add patch and sysconfig for Qualcomm Atheros QCA9564
> 
> Signed-off-by: Costa Yao <cqyao@qca.qualcomm.com>
> ---
>  WHENCE                       |    2 ++
>  ar3k/AthrBT_0x31010000.dfu   |  Bin 0 -> 38916 bytes
>  ar3k/ramps_0x31010000_40.dfu |  Bin 0 -> 1434 bytes
>  3 files changed, 2 insertions(+), 0 deletions(-)
>  create mode 100644 ar3k/AthrBT_0x31010000.dfu
>  create mode 100644 ar3k/ramps_0x31010000_40.dfu
[...]

Applied, thanks.

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2012-05-16 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Ac0jeFlvKx2HN5x8TrOEbxFWvA1PQA==>
2012-04-26  6:49 ` [PATCH] ar3k: add patch and sysconfig for QCA9564(Aphrodite) Yao, Costa
2012-05-11  9:12   ` Al Cho
2012-05-16 22:39   ` Ben Hutchings [this message]
2012-05-15  6:44 Yao, Costa

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=1337207944.4107.57.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=cqyao@qca.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=qca-linux-team@qualcomm.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).