From: Ben Hutchings <ben@decadent.org.uk>
To: "Li, Steven" <yongli@qca.qualcomm.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Chen, Jack" <skchen@qca.qualcomm.com>,
"Liu, Haijun" <haijun@qca.qualcomm.com>,
"Fan, Hong" <hongfan@qca.qualcomm.com>
Subject: Re: [PATCH] linux-firmware: Update patch and sysconfig files for AR3012.
Date: Tue, 12 Jul 2011 04:50:23 +0100 [thread overview]
Message-ID: <1310442623.8783.173.camel@localhost> (raw)
In-Reply-To: <1309769620-29044-1-git-send-email-Steven.Li@Atheros.com>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Mon, 2011-07-04 at 08:53 +0000, Li, Steven wrote:
> From: Steven.Li <yongli@qca.qualcomm.com>
>
> The new AR3012 keeps same PID/VID after downloading the patch and
> sysconfig files.
[...]
Is this change in behaviour backward-compatible with earlier versions of
the ath3k driver?
Also, please send a fix for the information in the WHENCE file. The
files are grouped by driver and then licence, so all the AR3012 files
should be listed in the existing section for the ath3k driver and not in
a separate section.
Ben.
--
Ben Hutchings
It is easier to write an incorrect program than to understand a correct one.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-07-12 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1309769620-29044-1-git-send-email-Steven.Li@Atheros.com>
2011-07-12 3:50 ` Ben Hutchings [this message]
[not found] <1311931587-28926-1-git-send-email-Steven.Li@Atheros.com>
[not found] ` <73DDB75979F36A42B75F3E2B6EB29434010525AB@nasanexd02c.na.qualcomm.com>
2011-07-29 9:59 ` [PATCH] linux-firmware: Update patch and sysconfig files for AR3012 David Woodhouse
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=1310442623.8783.173.camel@localhost \
--to=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=haijun@qca.qualcomm.com \
--cc=hongfan@qca.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=skchen@qca.qualcomm.com \
--cc=yongli@qca.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.