From: David Miller <davem@davemloft.net>
To: shemminger@linux-foundation.org
Cc: alan@lxorguk.ukuu.org.uk, netdev@vger.kernel.org
Subject: Re: [RFC] remove obsolete shaper code
Date: Wed, 22 Aug 2007 17:01:33 -0700 (PDT) [thread overview]
Message-ID: <20070822.170133.05603862.davem@davemloft.net> (raw)
In-Reply-To: <20070822165854.7a65f099@freepuppy.rosehill.hemminger.net>
From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Wed, 22 Aug 2007 16:58:54 -0700
> This driver is obsolete, and fixing it for adding upcoming changes
> to make hard_header_ops
> is problematic because it changes the underlying device handles.
>
> The driver has been superseded by iproute2/traffic control for
> a long time. Let's kill it.
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
Please do this with a proper feature-removal-schedule.txt entry and
timeframe.
next prev parent reply other threads:[~2007-08-23 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 23:58 [RFC] remove obsolete shaper code Stephen Hemminger
2007-08-23 0:01 ` David Miller [this message]
2007-08-23 16:44 ` [PATCH] shaper: mark for removal Stephen Hemminger
2007-08-25 6:10 ` David Miller
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=20070822.170133.05603862.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/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).