linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Thomas Pedersen <c_tpeder@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH] ath6kl: send TCMD response through testmode events
Date: Mon, 2 Jan 2012 18:54:25 +0200	[thread overview]
Message-ID: <4F01E141.1020903@qca.qualcomm.com> (raw)
In-Reply-To: <1325239020-6698-1-git-send-email-c_tpeder@qca.qualcomm.com>

On 12/30/2011 11:57 AM, Thomas Pedersen wrote:
> From: Thomas Pedersen <twpedersen@qca.qualcomm.com>
> 
> ath6kl no longer knows what it is transmitting through
> cfg80211_testmode, and simply passes opaque buffers between userspace
> and the firmware. Leave the CONT_RX enum for backwards compatibility.
> 
> Signed-off-by: Thomas Pedersen <twpedersen@qca.qualcomm.com>
> 
> v2:
> 	ath6kl_warn not _dbg, GFP_KERNEL, and misc. (Kalle)
> ---
>  drivers/net/wireless/ath/ath6kl/testmode.c |  104 +++++-----------------------
>  drivers/net/wireless/ath/ath6kl/testmode.h |    6 +-
>  drivers/net/wireless/ath/ath6kl/wmi.c      |    6 +-
>  3 files changed, 24 insertions(+), 92 deletions(-)

Please add the changelog after the "---" line, that way git does include
it to the commit log.

Thanks, patch applied with a minor change to return EOPNOTSUPP for
ATH6KL_TM_CMD_RX_REPORT. There's no need to support that command
anymore, keeping the entry in enum is enough.

Kalle

      reply	other threads:[~2012-01-02 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30  9:57 [PATCH] ath6kl: send TCMD response through testmode events Thomas Pedersen
2012-01-02 16:54 ` Kalle Valo [this message]

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=4F01E141.1020903@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=c_tpeder@qca.qualcomm.com \
    --cc=linux-wireless@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).