From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Add PID/VID support for AR1111
Date: Mon, 6 Aug 2012 11:20:09 +0530 [thread overview]
Message-ID: <501F5B11.3020406@qca.qualcomm.com> (raw)
In-Reply-To: <CAAT9HsjQ9abXWEy4Jp86HH9HUEOhSbQG_jn2Hnwk8_QX=oqfag@mail.gmail.com>
Hi Tim/Luis,
On Friday 03 August 2012 12:20 AM, Tim and Alison Bentley wrote:
> On 2 August 2012 19:13, John W. Linville <linville@tuxdriver.com> wrote:
>
>> On Thu, Aug 02, 2012 at 07:05:12PM +0100, Tim and Alison Bentley wrote:
>>> On 2 August 2012 18:43, Luis R. Rodriguez <rodrigue@qca.qualcomm.com>
>> wrote:
>>>
>>>> On Wed, Aug 1, 2012 at 11:28 PM, Mohammed Shafi Shajakhan
>>>> <mohammed@qca.qualcomm.com> wrote:
>>>>> From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>>>
>>>>> AR1111 is same as AR9485. The h/w
>>>>> difference between them is quite insignificant,
>>>>> Felix suggests only very few baseband features
>>>>> may not be available in AR1111. The h/w code for
>>>>> AR9485 is already present, so AR1111 should
>>>>> work fine with the addition of its PID/VID.
>>>>>
>>>>> Cc: stable at vger.kernel.org [2.6.39+]
>>>>> Cc: Felix Bitterli <felixb@qca.qualcomm.com>
>>>>> Reported-by: Tim and Alison Bentley <Home@trarbentley.net>
>>>>> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>>
>>>> Nice! I'd be happy with this going in once we get a Tested-by: report.
>>>> Dan, Tim?
>>>>
>>>>
>>>
>>> Will test tomorrow when I have time
>>
>> Hmmm...well, I just pushed it to wireless.git. I won't push it to
>> Dave until sometime tomorrow, to give a chance for some test.
>>
>> John
>> --
>> John W. Linville Someday the world will need a hero, and you
>> linville at tuxdriver.com might be all we have. Be ready.
>>
>
> Have tested patch and can confirm it is fine and works. (Connected now).
> Can you amend the reported by and Tested by lines to
> Tim Bentley <Tim.Bentley@Gmail.com>
> instead of the family email address.
> Sorry for any trouble.
>
thanks for testing this.
--
thanks,
shafi
WARNING: multiple messages have this Message-ID (diff)
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Tim and Alison Bentley <Home@TRARBentley.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
<linux-wireless@vger.kernel.org>, <ath9k-devel@venema.h4ckr.net>,
Felix Bitterli <felixb@qca.qualcomm.com>,
"Dan Williams" <dcbw@redhat.com>
Subject: Re: [PATCH] ath9k: Add PID/VID support for AR1111
Date: Mon, 6 Aug 2012 11:20:09 +0530 [thread overview]
Message-ID: <501F5B11.3020406@qca.qualcomm.com> (raw)
In-Reply-To: <CAAT9HsjQ9abXWEy4Jp86HH9HUEOhSbQG_jn2Hnwk8_QX=oqfag@mail.gmail.com>
Hi Tim/Luis,
On Friday 03 August 2012 12:20 AM, Tim and Alison Bentley wrote:
> On 2 August 2012 19:13, John W. Linville <linville@tuxdriver.com> wrote:
>
>> On Thu, Aug 02, 2012 at 07:05:12PM +0100, Tim and Alison Bentley wrote:
>>> On 2 August 2012 18:43, Luis R. Rodriguez <rodrigue@qca.qualcomm.com>
>> wrote:
>>>
>>>> On Wed, Aug 1, 2012 at 11:28 PM, Mohammed Shafi Shajakhan
>>>> <mohammed@qca.qualcomm.com> wrote:
>>>>> From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>>>
>>>>> AR1111 is same as AR9485. The h/w
>>>>> difference between them is quite insignificant,
>>>>> Felix suggests only very few baseband features
>>>>> may not be available in AR1111. The h/w code for
>>>>> AR9485 is already present, so AR1111 should
>>>>> work fine with the addition of its PID/VID.
>>>>>
>>>>> Cc: stable@vger.kernel.org [2.6.39+]
>>>>> Cc: Felix Bitterli <felixb@qca.qualcomm.com>
>>>>> Reported-by: Tim and Alison Bentley <Home@trarbentley.net>
>>>>> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>>
>>>> Nice! I'd be happy with this going in once we get a Tested-by: report.
>>>> Dan, Tim?
>>>>
>>>>
>>>
>>> Will test tomorrow when I have time
>>
>> Hmmm...well, I just pushed it to wireless.git. I won't push it to
>> Dave until sometime tomorrow, to give a chance for some test.
>>
>> John
>> --
>> John W. Linville Someday the world will need a hero, and you
>> linville@tuxdriver.com might be all we have. Be ready.
>>
>
> Have tested patch and can confirm it is fine and works. (Connected now).
> Can you amend the reported by and Tested by lines to
> Tim Bentley <Tim.Bentley@Gmail.com>
> instead of the family email address.
> Sorry for any trouble.
>
thanks for testing this.
--
thanks,
shafi
next prev parent reply other threads:[~2012-08-06 5:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 6:28 [ath9k-devel] [PATCH] ath9k: Add PID/VID support for AR1111 Mohammed Shafi Shajakhan
2012-08-02 6:28 ` Mohammed Shafi Shajakhan
2012-08-02 17:43 ` [ath9k-devel] " Luis R. Rodriguez
2012-08-02 17:43 ` Luis R. Rodriguez
2012-08-02 18:05 ` [ath9k-devel] " Tim and Alison Bentley
2012-08-02 18:13 ` John W. Linville
2012-08-02 18:13 ` John W. Linville
2012-08-02 18:50 ` [ath9k-devel] " Tim and Alison Bentley
2012-08-06 5:50 ` Mohammed Shafi Shajakhan [this message]
2012-08-06 5:50 ` Mohammed Shafi Shajakhan
2012-08-17 7:12 ` [ath9k-devel] : Sunil Mehta
2012-08-21 5:13 ` Mohammed Shafi Shajakhan
2012-09-20 10:37 ` Ravi Sharma
2012-09-20 10:37 ` Ravi Sharma
2012-09-24 5:15 ` Mohammed Shafi Shajakhan
2012-09-24 5:15 ` Mohammed Shafi Shajakhan
2012-09-24 14:40 ` Mohammed Shafi
2012-09-24 14:40 ` Mohammed Shafi
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=501F5B11.3020406@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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 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.