From: Florian Westphal <fw@strlen.de>
To: trix@redhat.com
Cc: pablo@netfilter.org, kadlec@netfilter.org, fw@strlen.de,
davem@davemloft.net, kuba@kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: conditionally use ct and ctinfo
Date: Mon, 7 Mar 2022 13:46:52 +0100 [thread overview]
Message-ID: <20220307124652.GB21350@breakpoint.cc> (raw)
In-Reply-To: <20220305180853.696640-1-trix@redhat.com>
trix@redhat.com <trix@redhat.com> wrote:
> From: Tom Rix <trix@redhat.com>
>
> The setting ct and ctinfo are controlled by
> CONF_NF_CONNTRACK. So their use should also
> be controlled.
Any reason for this change?
We try to avoid ifdef where possible, unless it avoids a compiler
warning/build/linker issue.
This doesn't change generated code for me (NF_CONNTRACK=n) either.
next prev parent reply other threads:[~2022-03-07 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 18:08 [PATCH] netfilter: conditionally use ct and ctinfo trix
2022-03-07 12:46 ` Florian Westphal [this message]
2022-03-07 13:39 ` Tom Rix
2022-03-07 21:54 ` Florian Westphal
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=20220307124652.GB21350@breakpoint.cc \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=trix@redhat.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 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.