From: Florian Westphal <fw@strlen.de>
To: David Miller <davem@davemloft.net>
Cc: marcel@holtmann.org, netdev@vger.kernel.org, aconole@bytheb.org,
fw@strlen.de, pablo@netfilter.org
Subject: Re: net-next tree broken with CONFIG_NETFILTER_INGRESS=n
Date: Wed, 5 Oct 2016 10:51:45 +0200 [thread overview]
Message-ID: <20161005085145.GA10576@breakpoint.cc> (raw)
In-Reply-To: <20161005.040137.1214181921027379179.davem@davemloft.net>
David Miller <davem@davemloft.net> wrote:
> From: Marcel Holtmann <marcel@holtmann.org>
> Date: Wed, 5 Oct 2016 09:48:42 +0200
>
> > I really wonder what is going on here. Normally if you break the
> > build, you fix it. However it seems nobody really cares enough. If I
> > am not mistaken, then this patch broke it:
>
> The people who can work on and merge the fix are travelling and
> conferencing in Tokyo right now, that's why this wasn't fixed
> instantaneously.
Seems the fix is rotting in nf-next....
prev parent reply other threads:[~2016-10-05 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 6:23 net-next tree broken with CONFIG_NETFILTER_INGRESS=n Marcel Holtmann
2016-10-05 7:48 ` Marcel Holtmann
2016-10-05 8:01 ` David Miller
2016-10-05 8:51 ` Florian Westphal [this message]
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=20161005085145.GA10576@breakpoint.cc \
--to=fw@strlen.de \
--cc=aconole@bytheb.org \
--cc=davem@davemloft.net \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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).