From: Florian Westphal <fw@strlen.de>
To: Stefan Agner <stefan@agner.ch>
Cc: stephen@networkplumber.org, davem@davemloft.net,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pablo@netfilter.org
Subject: Re: [PATCH] netfilter: bridge: clarify bridge/netfilter message
Date: Thu, 29 Sep 2016 04:25:20 +0200 [thread overview]
Message-ID: <20160929022520.GH17426@breakpoint.cc> (raw)
In-Reply-To: <20160928220528.17478-1-stefan@agner.ch>
Stefan Agner <stefan@agner.ch> wrote:
> When using bridge without bridge netfilter enabled the message
> displayed is rather confusing and leads to belive that a deprecated
> feature is in use. Use IS_MODULE to be explicit that the message only
> affects users which use bridge netfilter as module and reword the
> message.
Acked-by: Florian Westphal <fw@strlen.de>
next prev parent reply other threads:[~2016-09-29 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 22:05 [PATCH] netfilter: bridge: clarify bridge/netfilter message Stefan Agner
2016-09-29 2:25 ` Florian Westphal [this message]
2016-10-03 2:44 ` David Miller
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=20160929022520.GH17426@breakpoint.cc \
--to=fw@strlen.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stefan@agner.ch \
--cc=stephen@networkplumber.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).