From: Kalle Valo <kvalo@codeaurora.org>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/6] ath9k patches
Date: Thu, 29 Jan 2015 10:37:21 +0200 [thread overview]
Message-ID: <878ugm3rum.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1422447866-19967-1-git-send-email-sujith@msujith.org> (Sujith Manoharan's message of "Wed, 28 Jan 2015 17:54:20 +0530")
Sujith Manoharan <sujith@msujith.org> writes:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> ath9k patches for -next.
>
> v2 - Fix typo in patch "ath9k: Add a macro to identify PCOEM chips".
>
> Sujith Manoharan (6):
> ath9k: Update QCA953x initvals
> ath9k: Update AR955x initvals
> ath9k: Add a macro to identify PCOEM chips
> ath9k: Fix manual peak calibration initialization
> ath9k: Set correct peak detect threshold
> ath9k: Enable manual peak detect calibration
Thanks, all six applied to wireless-drivers-next.git.
--
Kalle Valo
next prev parent reply other threads:[~2015-01-29 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 12:24 [PATCH v2 0/6] ath9k patches Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 1/6] ath9k: Update QCA953x initvals Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 2/6] ath9k: Update AR955x initvals Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 3/6] ath9k: Add a macro to identify PCOEM chips Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 4/6] ath9k: Fix manual peak calibration initialization Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 5/6] ath9k: Set correct peak detect threshold Sujith Manoharan
2015-01-28 12:24 ` [PATCH v2 6/6] ath9k: Enable manual peak detect calibration Sujith Manoharan
2015-01-29 8:37 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-07 4:44 [PATCH v2 0/6] ath9k patches Sujith Manoharan
2014-09-03 3:09 Sujith Manoharan
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=878ugm3rum.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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).