From: David Miller <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: shemminger@osdl.org, netdev@vger.kernel.org,
kuznet@ms2.inr.ac.ru, herbert@gondor.apana.org.au
Subject: Re: [RFC][NET::SCHED]: cleanup qdisc_restart
Date: Mon, 14 Aug 2006 16:00:16 -0700 (PDT) [thread overview]
Message-ID: <20060814.160016.23014480.davem@davemloft.net> (raw)
In-Reply-To: <1155596247.6946.9.camel@jzny2>
From: jamal <hadi@cyberus.ca>
Date: Mon, 14 Aug 2006 18:57:27 -0400
> The question to ask though is: shouldnt we be having drivers use the
> mnemonics instead of values like 1?
Absolutely, but while such conversions still remain undone
we shouldn't knowingly break stuff :)
prev parent reply other threads:[~2006-08-14 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 18:43 [RFC][NET::SCHED]: cleanup qdisc_restart jamal
2006-08-15 14:42 ` Stephen Hemminger
2006-08-14 21:01 ` David Miller
2006-08-14 22:57 ` jamal
2006-08-14 23:00 ` David Miller [this message]
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=20060814.160016.23014480.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).