From: Bala Shanmugam <sbalashanmugam@atheros.com>
To: Shanmugamkamatchi Balashanmugam
<Shanmugamkamatchi.Balashanmugam@Atheros.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] linux-firmware: Add patch and sysconfig files for AR3012.
Date: Tue, 15 Feb 2011 14:53:49 +0530 [thread overview]
Message-ID: <4D5A4625.4060104@atheros.com> (raw)
In-Reply-To: <1297248851-14996-1-git-send-email-sbalashanmugam@atheros.com>
Hi David,
On 2/9/2011 4:24 PM, Shanmugamkamatchi Balashanmugam wrote:
> Signed-off-by: Bala Shanmugam<sbalashanmugam@atheros.com>
> ---
> WHENCE | 9 +++++++++
> ar3k/AthrBT_0x01020001.dfu | Bin 0 -> 55244 bytes
> ar3k/ramps_0x01020001_26.dfu | Bin 0 -> 1224 bytes
> 3 files changed, 9 insertions(+), 0 deletions(-)
> create mode 100644 ar3k/AthrBT_0x01020001.dfu
> create mode 100644 ar3k/ramps_0x01020001_26.dfu
>
> diff --git a/WHENCE b/WHENCE
> index 1cbd0a6..2de0bea 100644
> --- a/WHENCE
> +++ b/WHENCE
> @@ -1534,3 +1534,12 @@ Driver: vt6656 - VIA VT6656 USB wireless driver
> File: vntwusb.fw
>
> Licence: Redistributable. See LICENCE.via_vt6656 for details.
> +
> +--------------------------------------------------------------------------
> +
> +Driver: DFU Driver for Atheros bluetooth chipset AR3012
> +
> +File: ar3k/AthrBT_0x01020001.dfu
> +File: ar3k/ramps_0x01020001_26.dfu
> +
Driver changes for AR3012 have been upstreamed.
Can you please upstream above patch?
Regards,
Bala.
next prev parent reply other threads:[~2011-02-15 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 10:54 [PATCH] linux-firmware: Add patch and sysconfig files for AR3012 Bala Shanmugam
2011-02-15 9:23 ` Bala Shanmugam [this message]
2011-03-01 6:41 ` Bala Shanmugam
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=4D5A4625.4060104@atheros.com \
--to=sbalashanmugam@atheros.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
--cc=dwmw2@infradead.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;
as well as URLs for NNTP newsgroup(s).