From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: andi@firstfloor.org, netdev@vger.kernel.org,
schwidefsky@de.ibm.com, 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 21:38:49 -0400 [thread overview]
Message-ID: <20120516013849.GA26701@windriver.com> (raw)
In-Reply-To: <20120515.210020.1631343759962418692.davem@davemloft.net>
[Re: [PATCH/RFC net-next 0/4] Delete token ring support.] On 15/05/2012 (Tue 21:00) David Miller wrote:
> From: Andi Kleen <andi@firstfloor.org>
> Date: Tue, 15 May 2012 17:48:15 -0700
>
> > 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.
3c501.c is on my radar. The 8bit ISA hardware with discrete TTL
components everywhere was crap back in the early 1990s, and it sure as
hell has not got better with age.
>
> I also support removing the token ring stuff, and in fact I'm more
> than happy to add your patch set to the net-next tree right now.
Great -- that was the kind of response I was hoping for, but not
expecting to get. Let me run one last allyesconfig/allmodconfig
and I'll send a pull request. I've already run the defconfig
build on s390 to make sure I didn't break them.
Thanks,
Paul.
next prev parent reply other threads:[~2012-05-16 1:38 UTC|newest]
Thread overview: 9+ 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:48 ` [PATCH/RFC net-next 0/4] Delete " Andi Kleen
2012-05-16 1:00 ` David Miller
2012-05-16 1:38 ` Paul Gortmaker [this message]
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=20120516013849.GA26701@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=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=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).