From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: "Andrew G. Morgan" <morgan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ben Nizette <bn@niasdigital.com>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: BUG: 2.6.25-rc1: iptables postrouting setup causes oops
Date: Wed, 13 Feb 2008 19:19:40 +0100 [thread overview]
Message-ID: <20080213191940.7e0aa018@siona> (raw)
In-Reply-To: <47B31DE7.9060400@kernel.org>
On Wed, 13 Feb 2008 08:42:15 -0800
"Andrew G. Morgan" <morgan@kernel.org> wrote:
> However, it is a warning and, for any existing app that doesn't care
> about newly added capabilities, the warning is benign.
Ok, I see. Thanks for explaining.
Haavard
next prev parent reply other threads:[~2008-02-13 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 11:46 BUG: 2.6.25-rc1: iptables postrouting setup causes oops Ben Nizette
2008-02-13 8:48 ` Andrew Morton
2008-02-13 9:10 ` Haavard Skinnemoen
2008-02-13 9:22 ` Andrew Morton
2008-02-13 16:42 ` Andrew G. Morgan
2008-02-13 18:19 ` Haavard Skinnemoen [this message]
2008-02-13 11:29 ` Haavard Skinnemoen
2008-02-13 22:41 ` Ben Nizette
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=20080213191940.7e0aa018@siona \
--to=hskinnemoen@atmel.com \
--cc=akpm@linux-foundation.org \
--cc=bn@niasdigital.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.