From: Paul Bolle <pebolle@tiscali.nl>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"John W. Linville" <linville@tuxdriver.com>,
Oleksij Rempel <linux@rempel-privat.de>,
Richard Weinberger <richard@nod.at>,
Jonathan Bither <jonbither@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
ath5k-devel@venema.h4ckr.net, open@hauke-m.de,
"list@hauke-m.de:NETWORKING DRIVERS" <list@hauke-m.de>,
"antonynpavlov@gmail.com" <antonynpavlov@gmail.com>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"list@hauke-m.de:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 09/28] Remove ATHEROS_AR231X
Date: Wed, 18 Jun 2014 13:46:14 +0200 [thread overview]
Message-ID: <1403091974.1984.102.camel@x220> (raw)
In-Reply-To: <CAHNKnsSfaT7xC5_wv=TrGLEQ2pjC91Q1XG891_n64OuR0fA9Jg@mail.gmail.com>
Hi Sergey,
On Wed, 2014-06-18 at 15:10 +0400, Sergey Ryazanov wrote:
> 2014-06-18 14:25 GMT+04:00 Paul Bolle <pebolle@tiscali.nl>:
> > ATHEROS_AR231X and the things depending on it, like AHB bus support,
> > have been discussed for three years now. When will you (re)consider a
> > patch to remove all currently dead code?
> >
> > And to state the obvious: AHB bus support, and the other code depending
> > on ATHEROS_AR231X, can always be re-added once ATHEROS_AR231X gets added
> > to the tree.
>
> Work in progress, I don't stop it. Just work is progressing slower
> than I had planned. I am already cleanup the code (mostly checkpatch
> errors and warnings) and send patches to OpenWRT tree. Further I plan
> to simplify initialization and I will be ready to send patches
> upstream.
That's good to hear.
> I need a couple of weeks for this. Is its reasonable time to not make
> a mess of remove/add commits?
Removing the code just to re-add it shortly after would indeed be
awkward.
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?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2014-06-18 11:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391971686-9517-1-git-send-email-richard@nod.at>
2014-02-09 18:47 ` [PATCH 09/28] Remove ATHEROS_AR231X Richard Weinberger
2014-02-09 19:09 ` Joe Perches
2014-02-09 19:43 ` Paul Bolle
[not found] ` <52F7D480.1050106@hauke-m.de>
2014-02-09 20:03 ` Richard Weinberger
2014-02-10 12:05 ` Sergey Ryazanov
2014-02-10 12:17 ` Oleksij Rempel
2014-02-10 12:38 ` Sergey Ryazanov
2014-02-10 22:37 ` Florian Fainelli
2014-02-10 23:43 ` Sergey Ryazanov
2014-02-12 10:50 ` Sergey Ryazanov
2014-02-13 20:14 ` John W. Linville
2014-04-15 17:08 ` Paul Bolle
2014-04-16 9:20 ` Sergey Ryazanov
2014-06-18 10:25 ` Paul Bolle
2014-06-18 11:10 ` Sergey Ryazanov
2014-06-18 11:46 ` Paul Bolle [this message]
2014-06-18 13:15 ` [ath5k-devel] " Holger Schurig
2014-06-18 13:42 ` Paul Bolle
2014-09-05 10:10 ` Paul Bolle
2014-09-05 11:12 ` Sergey Ryazanov
2014-09-05 11:33 ` Paul Bolle
2014-09-05 12:02 ` Sergey Ryazanov
2014-09-09 18:27 ` John W. Linville
2014-09-10 8:53 ` [PATCH] [RESEND] ath5k: Remove AHB bus support Paul Bolle
2014-09-26 17:45 ` John W. Linville
2014-09-10 10:33 ` [PATCH 09/28] Remove ATHEROS_AR231X Sergey Ryazanov
2014-09-10 11:36 ` Jiri Slaby
2014-09-10 12:19 ` Sergey Ryazanov
2014-09-11 19:21 ` John W. Linville
2014-09-15 18:45 ` John W. Linville
2014-09-16 20:26 ` Paul Bolle
2014-09-16 20:33 ` John W. Linville
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=1403091974.1984.102.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=antonynpavlov@gmail.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=hauke@hauke-m.de \
--cc=jirislaby@gmail.com \
--cc=jonbither@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=linville@tuxdriver.com \
--cc=list@hauke-m.de \
--cc=mcgrof@do-not-panic.com \
--cc=mickflemm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=open@hauke-m.de \
--cc=openwrt-devel@lists.openwrt.org \
--cc=richard@nod.at \
--cc=ryazanov.s.a@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).