From: Andi Kleen <andi@firstfloor.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH/RFC net-next 0/4] Delete token ring support.
Date: Tue, 15 May 2012 17:48:15 -0700 [thread overview]
Message-ID: <m2k40dkl2o.fsf@firstfloor.org> (raw)
In-Reply-To: <1337128544-18680-1-git-send-email-paul.gortmaker@windriver.com> (Paul Gortmaker's message of "Tue, 15 May 2012 20:35:40 -0400")
Paul Gortmaker <paul.gortmaker@windriver.com> writes:
>
> What I mean by (2) is the implicit absence of anyone fixing _runtime_
> bugs, going all the way back to 2.6.12 in 2005. If the code was being
> _used_, we'd see runtime regressions reported and their associated
> fixes.
Removal sounds good to me. In fact I would argue to remove any other driver
which did not get a real change since 2005 too.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-05-16 0:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 0:35 [PATCH/RFC net-next 0/4] Delete token ring support Paul Gortmaker
2012-05-16 0:35 ` [PATCH net-next 1/4] s390: delete any traces of " Paul Gortmaker
2012-05-16 0:35 ` [PATCH net-next 2/4] atm: remove the coupling to " Paul Gortmaker
2012-05-16 0:35 ` [PATCH net-next 3/4] net: delete all instances of special processing for token ring Paul Gortmaker
2012-05-16 0:35 ` [PATCH net-next 4/4] tokenring: delete all remaining driver support Paul Gortmaker
2012-05-16 0:48 ` Andi Kleen [this message]
2012-05-16 1:00 ` [PATCH/RFC net-next 0/4] Delete token ring support David Miller
2012-05-16 1:38 ` Paul Gortmaker
2012-05-16 3:05 ` Paul Gortmaker
2012-05-16 5:04 ` David Miller
2012-05-16 7:43 ` Martin Schwidefsky
2012-05-16 9:29 ` Bjørn Mork
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=m2k40dkl2o.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=schwidefsky@de.ibm.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).