Linux wireless drivers development
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath6kl: Make ath6kl_diag_write32() non-static
Date: Mon, 5 Sep 2011 14:24:25 +0530	[thread overview]
Message-ID: <20110905085424.GA11758@vasanth-laptop> (raw)
In-Reply-To: <4E6486B5.9070105@qca.qualcomm.com>

On Mon, Sep 05, 2011 at 11:22:13AM +0300, Kalle Valo wrote:
> On 09/02/2011 04:46 PM, Vasanthakumar Thiagarajan wrote:
> > So that this can be called from debug.c when adding support
> > to write chip register.
> 
> Thanks, all three applied. But I did a minor to change to patch 3:
> 
> Author: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
> Date:   Mon Sep 5 11:19:46 2011 +0300
> 
>     ath6kl: Add debugfs support to write a chip register
> 
>     To write a value to register:
>     echo <register_offset>=<register_value> >
> <degfs_root>/ieee80211/phyX/ath6kl/reg_write
> 
>     kvalo: rename file to reg_write to follow the style of other debugfs
> files

Thanks.

Vasanth

      reply	other threads:[~2011-09-05  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 13:46 [PATCH 1/3] ath6kl: Make ath6kl_diag_write32() non-static Vasanthakumar Thiagarajan
2011-09-02 13:46 ` [PATCH 2/3] ath6kl: Fix endianness in register write Vasanthakumar Thiagarajan
2011-09-02 13:46 ` [PATCH 3/3] ath6kl: Add debugfs support to write a chip register Vasanthakumar Thiagarajan
2011-09-05  8:22 ` [PATCH 1/3] ath6kl: Make ath6kl_diag_write32() non-static Kalle Valo
2011-09-05  8:54   ` Vasanthakumar Thiagarajan [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=20110905085424.GA11758@vasanth-laptop \
    --to=vthiagar@qca.qualcomm.com \
    --cc=kvalo@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