Re: [PATCH 09/28] Remove ATHEROS_AR231X
From: John W. Linville <hidden>
Date: 2014-09-09 18:30:18
Also in:
linux-wireless, lkml
Possibly related (same subject, not in this thread)
- 2014-02-09 · Re: [PATCH 09/28] Remove ATHEROS_AR231X · Paul Bolle <hidden>
- 2014-02-09 · Re: [PATCH 09/28] Remove ATHEROS_AR231X · Joe Perches <joe@perches.com>
- 2014-02-09 · [PATCH 09/28] Remove ATHEROS_AR231X · Richard Weinberger <richard@nod.at>
On Fri, Sep 05, 2014 at 04:02:10PM +0400, Sergey Ryazanov wrote:
2014-09-05 15:33 GMT+04:00 Paul Bolle [off-list ref]:quoted
Hi Sergey, On Fri, 2014-09-05 at 15:12 +0400, Sergey Ryazanov wrote:quoted
2014-09-05 14:10 GMT+04:00, Paul Bolle [off-list ref]:quoted
On Wed, 2014-06-18 at 13:46 +0200, Paul Bolle wrote:quoted
Having this conversation every rc1 is getting a bit silly. Could Jiri e.a. perhaps set some specific deadline for ATHEROS_AR231X to be submitted?I waited until rc3. Have you seen any activity on this front? If not, should I resend the patch that removes the code in mainline that depends on ATHEROS_AR231X (ie, AHB bus support)?Recent activity always could be found in [1]. Now I finish another one round of cleanups and have a plan to fix several things (you can always find something that you really want to improve). But if you insist I could immediately switch to "send upstream" mode. And seems that this would be better approach. 1. https://dev.openwrt.org/log/trunk/target/linux/atherosAnd where can the related PULL requests or patch submissions be found?I have not sent patches yet, since I thought that it would be easier to cleanup them in openwrt tree and then send them upstream.
That excuse has worn a bit thin. Perhaps Paul should repost his removal and you can add a revert to the start of your patch series? John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.