ath9k|ath9k_htc: move dups to common-beacon
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 23 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 23 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [ath9k-devel] [PATCH 00/23] ath9k|ath9k_htc: move dups to common-beacon
Quoted 6 lines · Sujith Manoharan
Quoted 4 lines · Oleksij Rempel
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.
Quoted 8 lines
Sure. It is just another option to consider.
Quoted 3 lines
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?
Signature · 2 lines
John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready.