Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-devel Digest, Vol 79, Issue 6
Date: Fri, 9 Jan 2015 11:01:01 +0100	[thread overview]
Message-ID: <54AFA6DD.50905@broadcom.com> (raw)
In-Reply-To: <tencent_7FC7BFD37BFF78153CE89B15@qq.com>

On 01/09/15 02:54, ??? wrote:
> Hi Arend,
> I had ATH9k hardware, my wireless device is WLE350NX, it is AR9580 chip.
> Please send me your code to test!
> I am new to LINUX.

Ok. The patch can be found on patchwork [1]. That page contains download 
links to get the patch. _mbox_ link can be used with 'git am' command. 
_patch_ link can be used with 'patch' command.

Regards,
Arend

[1] https://patchwork.kernel.org/patch/5544621/

> Regards,
> David Yang
> ------------------ Original ------------------
> *From: * "ath9k-devel-request"<ath9k-devel-request@lists.ath9k.org>;
> *Date: * Thu, Jan 8, 2015 07:00 PM
> *To: * "ath9k-devel"<ath9k-devel@lists.ath9k.org>;
> *Subject: * ath9k-devel Digest, Vol 79, Issue 6
> Send ath9k-devel mailing list submissions to
> ath9k-devel at lists.ath9k.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> or, via email, send a message with subject or body 'help' to
> ath9k-devel-request at lists.ath9k.org
>
> You can reach the person managing the list at
> ath9k-devel-owner at lists.ath9k.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ath9k-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: [PATCH] ath: ath9k: use debugfs_create_devm_seqfile()
> helper for seq_file entries (Kalle Valo)
> 2. Re: [PATCH] ath: ath9k: use debugfs_create_devm_seqfile()
> helper for seq_file entries (Sujith Manoharan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 07 Jan 2015 20:05:00 +0200
> From: Kalle Valo <kvalo@codeaurora.org>
> Subject: Re: [ath9k-devel] [PATCH] ath: ath9k: use
> debugfs_create_devm_seqfile() helper for seq_file entries
> To: Arend van Spriel <arend@broadcom.com>
> Cc: ath9k-devel at lists.ath9k.org, linux-wireless
> <linux-wireless@vger.kernel.org>
> Message-ID: <87bnmapiur.fsf@kamboji.qca.qualcomm.com>
> Content-Type: text/plain; charset=us-ascii
>
> Arend van Spriel <arend@broadcom.com> writes:
>
>  > Use the helper to get rid of the file operations per debugfs file. The
>  > device driver data contains struct ieee80211_hw pointer and the
>  > struct ath9k_softc pointer is assigned to ieee80211_hw::priv so it can
>  > be accessed in the seq_file read operation.
>  >
>  > Cc: ath9k-devel at lists.ath9k.org
>  > Signed-off-by: Arend van Spriel <arend@broadcom.com>
>  > ---
>  > Hi Kalle,
>  >
>  > This patch was reverted in the driver-core repository as I overlooked
>  > the use of driver data and caused ath9k driver to crash. I believe this
>  > revised patch properly uses it now although I have no ath9k hardware to
>  > test this. So I hope some ath9k developers out there can give this patch
>  > a run for its money. It compiles and no checkpatch or sparse warnings.
>  >
>  > The patch applies to the master branch of the wireless-drivers-next
>  > repository.
>
> Can someone with ath9k hardware test this, please? I'm hesitant to apply
> this without testing.
>
> --
> Kalle Valo
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 8 Jan 2015 08:49:00 +0530
> From: Sujith Manoharan <sujith@msujith.org>
> Subject: Re: [ath9k-devel] [PATCH] ath: ath9k: use
> debugfs_create_devm_seqfile() helper for seq_file entries
> To: Kalle Valo <kvalo@codeaurora.org>
> Cc: Arend van Spriel <arend@broadcom.com>,
> ath9k-devel at lists.ath9k.org, linux-wireless
> <linux-wireless@vger.kernel.org>
> Message-ID: <21677.63268.657151.679992@gargle.gargle.HOWL>
> Content-Type: text/plain; charset=us-ascii
>
>  > Arend van Spriel <arend@broadcom.com> writes:
>  >
>  > > Use the helper to get rid of the file operations per debugfs file. The
>  > > device driver data contains struct ieee80211_hw pointer and the
>  > > struct ath9k_softc pointer is assigned to ieee80211_hw::priv so it can
>  > > be accessed in the seq_file read operation.
>  > >
>  > > Cc: ath9k-devel at lists.ath9k.org
>  > > Signed-off-by: Arend van Spriel <arend@broadcom.com>
>
> Thanks for the patch.
>
>  > Can someone with ath9k hardware test this, please? I'm hesitant to apply
>  > this without testing.
>
> I tested it and there were no crashes.
>
> Sujith
>
>
> ------------------------------
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
> End of ath9k-devel Digest, Vol 79, Issue 6
> ******************************************

  reply	other threads:[~2015-01-09 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1420714802.32497.ath9k-devel@lists.ath9k.org>
2015-01-09  1:54 ` [ath9k-devel] ath9k-devel Digest, Vol 79, Issue 6 杨铁军
2015-01-09 10:01   ` Arend van Spriel [this message]
2015-01-10  2:00     ` 杨铁军
2015-01-10 11:50       ` Arend van Spriel

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=54AFA6DD.50905@broadcom.com \
    --to=arend@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox