From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 00/23] ath9k|ath9k_htc: move dups to common-beacon
Date: Thu, 6 Mar 2014 13:42:35 -0500 [thread overview]
Message-ID: <20140306184235.GA7788@tuxdriver.com> (raw)
In-Reply-To: <21266.58035.719712.344551@gargle.gargle.HOWL>
On Sun, Mar 02, 2014 at 01:20:11PM +0530, Sujith Manoharan wrote:
> Oleksij Rempel wrote:
> > I was thinking about it too, but suddenly i don't have enough time and
> > experience to do it. Beside, there is no need to write usb layer. It is
> > clean and separate from other part of the driver. But the HTC/WMI
> > interface is not completely separate.
>
> Sure. It is just another option to consider.
>
> > Now about bigger picture. Right now i work only on ath9k<>ath9k_htc
> > dups. But there are lots of dup code in ath9k itself. For example
> > *_phy.c, *_initvals.h. Here are some examples:
>
> We already have duplicate detection for initvals. It is part of
> the initvals tool in qca-swiss-army-knife.
So, where does this leave us? Should this series be merged? Or not?
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-03-06 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1393704966-13985-1-git-send-email-linux@rempel-privat.de>
[not found] ` <21266.37896.937680.416439@gargle.gargle.HOWL>
2014-03-02 7:27 ` [ath9k-devel] [PATCH 00/23] ath9k|ath9k_htc: move dups to common-beacon Oleksij Rempel
2014-03-02 7:50 ` Sujith Manoharan
2014-03-06 18:42 ` John W. Linville [this message]
2014-03-07 9:55 ` Oleksij Rempel
2014-03-07 10:18 ` Sujith Manoharan
2014-03-10 15:08 ` Oleksij Rempel
2014-03-14 19:22 ` John W. Linville
2014-03-15 7:51 ` Oleksij Rempel
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=20140306184235.GA7788@tuxdriver.com \
--to=linville@tuxdriver.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