netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	David Miller <davem@davemloft.net>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: RAW netfilter - "advanced netfilter setting" or not?
Date: Thu, 24 Nov 2011 08:11:56 +0100	[thread overview]
Message-ID: <4ECDEE3C.1030306@trash.net> (raw)
In-Reply-To: <CA+55aFxPHAf7DDD4cd3ZHNhwdbV4ijSZz83U5=5BzYqgiVKdtg@mail.gmail.com>

On 23.11.2011 23:58, Linus Torvalds wrote:
> On Wed, Nov 23, 2011 at 2:32 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
>>
>> Right, but how would you decide what will be enabled/disabled by
>> default? It seems unlikely you will be adding a patch (like Dave's)
>> everytime a default distro installation throws certain errors once
>> you run your own kernel configs.
> 
> I do think that "major distributions do this by default" should simply
> be the point for deciding it. Nothing more, nothing less.

Agreed, that's also the criteria we used when we introduced this option.

  reply	other threads:[~2011-11-24  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 19:45 RAW netfilter - "advanced netfilter setting" or not? Linus Torvalds
2011-11-23 19:58 ` Patrick McHardy
2011-11-23 20:17   ` Linus Torvalds
2011-11-23 20:51     ` richard -rw- weinberger
2011-11-23 21:27 ` Jan Engelhardt
2011-11-23 22:02   ` Linus Torvalds
2011-11-23 22:32     ` Jan Engelhardt
2011-11-23 22:58       ` Linus Torvalds
2011-11-24  7:11         ` Patrick McHardy [this message]
     [not found] <CA+55aFzvZowH1_bA66VZ5Aw0wF3KzdGSqiNZLw46J3u4gpKnxA@mail.gmail.com>
2011-11-23 21:07 ` David Miller
2011-11-23 22:02   ` Linus Torvalds
2011-12-02  3:12   ` Linus Torvalds
2011-12-02  3:18     ` 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=4ECDEE3C.1030306@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=torvalds@linux-foundation.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).