From: "David S. Miller" <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: kaber@trash.net, 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: Fri, 10 Mar 2006 03:04:22 -0800 (PST) [thread overview]
Message-ID: <20060310.030422.127226482.davem@davemloft.net> (raw)
In-Reply-To: <1141498341.5185.32.camel@localhost.localdomain>
From: jamal <hadi@cyberus.ca>
Date: Sat, 04 Mar 2006 13:52:21 -0500
> So on Adrian's patch and above reasoning:
>
> ACKed-by: Jamal Hadi Salim <hadi@cyberus.ca>
Applied, thanks Adrian.
next prev parent reply other threads:[~2006-03-10 11:04 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
2006-03-04 20:36 ` Patrick McHardy
2006-03-10 11:04 ` David S. Miller [this message]
-- 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=20060310.030422.127226482.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@stusta.de \
--cc=hadi@cyberus.ca \
--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).