From: Andi Kleen <ak@suse.de>
To: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, davem@redhat.com
Subject: Re: status of ipchains in 2.6?
Date: 28 Oct 2003 15:31:09 +0100 [thread overview]
Message-ID: <p733cdda0ya.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20031028090304.GA19302@lps.ens.fr.suse.lists.linux.kernel>
Éric Brunet <Eric.Brunet@lps.ens.fr> writes:
>
> In my case, 2.6.0-test4 is working fine.
Can you do a binary search in the versions to see which version
broke it?
test5-test8 all had netfilter changes.
-Andi
next parent reply other threads:[~2003-10-28 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310280127.h9S1RM5d002140@napali.hpl.hp.com.suse.lists.linux.kernel>
[not found] ` <20031028090304.GA19302@lps.ens.fr.suse.lists.linux.kernel>
2003-10-28 14:31 ` Andi Kleen [this message]
[not found] <200310280127.h9S1RM5d002140@napali.hpl.hp.com>
2003-10-28 9:50 ` status of ipchains in 2.6? David S. Miller
2003-10-28 17:56 ` David Mosberger
2003-10-28 17:57 ` David S. Miller
2003-10-28 19:25 ` David Mosberger
2003-10-28 18:23 ` Martin Josefsson
2003-10-29 0:16 ` David Mosberger
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=p733cdda0ya.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=Eric.Brunet@lps.ens.fr \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).