linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH] ath6kl: Fix missing gpio pin 9 configuration
Date: Wed, 23 May 2012 10:18:45 +0300	[thread overview]
Message-ID: <4FBC8F55.3080509@qca.qualcomm.com> (raw)
In-Reply-To: <4FBC8EBF.20404@qca.qualcomm.com>

On 05/23/2012 10:16 AM, Vasanthakumar Thiagarajan wrote:
> On Tuesday 22 May 2012 12:52 PM, Vasanthakumar Thiagarajan wrote:
>> GPIO pin 9 also needs to be configured along with other gpio
>> pins to avoid sdio crc errors. I've not experienced any issue
>> with missing this particular gpio pin configuration, found dunring
>> code review. This can potentially improve rx performance.
>>
>> Signed-off-by: Vasanthakumar Thiagarajan<vthiagar@qca.qualcomm.com>
>
> I hope you are not dropping this one along with the other
> series of two patches sent mistakenly. This is genuine patch.

No, I didn't. I was just busy with something else, will review soon.

Kalle

  reply	other threads:[~2012-05-23  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  7:22 [PATCH] ath6kl: Fix missing gpio pin 9 configuration Vasanthakumar Thiagarajan
2012-05-22  7:22 ` [PATCH 1/2] ath6kl: Update netstats for some of the tx failrues in ath6kl_data_tx() Vasanthakumar Thiagarajan
2012-05-22  7:22 ` [PATCH 2/2] ath6kl: Complete failed tx packet in ath6kl_htc_tx_from_queue() Vasanthakumar Thiagarajan
2012-05-22  7:25   ` Vasanthakumar Thiagarajan
2012-05-22 12:28     ` Kalle Valo
2012-05-23  7:16 ` [PATCH] ath6kl: Fix missing gpio pin 9 configuration Vasanthakumar Thiagarajan
2012-05-23  7:18   ` Kalle Valo [this message]
2012-05-24  7:13 ` Kalle Valo

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=4FBC8F55.3080509@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vthiagar@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 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).