From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Adrian Bunk <bunk@stusta.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] let NET_CLS_ACT no longer depend on EXPERIMENTAL
Date: Sat, 04 Mar 2006 13:52:21 -0500 [thread overview]
Message-ID: <1141498341.5185.32.camel@localhost.localdomain> (raw)
In-Reply-To: <4409C6BA.60803@trash.net>
On Sat, 2006-04-03 at 17:56 +0100, Patrick McHardy wrote:
> Adrian Bunk wrote:
> > This option should IMHO no longer depend on EXPERIMENTAL.
> >
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > ---
> >
> > This patch was already sent on:
> > - 12 Feb 2006
>
> Yesterday I managed to crash my machine playing around with tc actions
> within minutes. I haven't looked into it yet, but it seems it still
> needs more testing.
Simple: Fix the bug and submit a patch. If you cant find the cause post
what you are doing.
What is the metric for going from experimental to non-experimental?
I surely hope it doesnt come to some irrational reasoning like
"Patrick found a bug"[1].
- It has been around since 2.6.7/8;
- I use it extensively on about 10 machines since (I am pretty sure a
lot more extensively than Patrick)
- I know people who use it extensively
- I am pretty sure there are people that i dont know who use it
extensively
So on Adrian's patch and above reasoning:
ACKed-by: Jamal Hadi Salim <hadi@cyberus.ca>
cheers,
jamal
[1]If you used half of that logic on netfilter it would still be
experimental or rather should be demoted to experimental.
next prev parent reply other threads:[~2006-03-04 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 16:07 [RFC: 2.6 patch] let NET_CLS_ACT no longer depend on EXPERIMENTAL Adrian Bunk
2006-03-04 16:56 ` Patrick McHardy
2006-03-04 18:52 ` jamal [this message]
2006-03-04 20:36 ` Patrick McHardy
2006-03-10 11:04 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-02-12 17:56 Adrian Bunk
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=1141498341.5185.32.camel@localhost.localdomain \
--to=hadi@cyberus.ca \
--cc=bunk@stusta.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).