From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Arnd Bergmann <arnd@arndb.de>, Florian Westphal <fw@strlen.de>
Subject: Rebasing nf-next...
Date: Tue, 1 Nov 2016 20:37:00 +0100 [thread overview]
Message-ID: <20161101193700.GA17249@salvia> (raw)
Hi,
I'm rebasing nf-next because I found problems on the ipset batch.
As part of the rebase, I'm going to squash this Arnd's patch:
http://patchwork.ozlabs.org/patch/688615/
into original Florian's fib nf_tables expression patch.
As well as this one:
http://patchwork.ozlabs.org/patch/689267/
into the nf_socket lookup infrastructure.
Given I'm rebasing, I don't think it's useful to keep those around
after the rebase to upstream this to David's net-next.
Sorry.
next reply other threads:[~2016-11-01 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 19:37 Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-06 20:57 Rebasing nf-next Pablo Neira Ayuso
2018-01-08 15:45 Pablo Neira Ayuso
2019-07-03 19:16 Pablo Neira Ayuso
2020-03-12 13:43 rebasing nf-next Pablo Neira Ayuso
2021-05-28 19:10 Pablo Neira Ayuso
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=20161101193700.GA17249@salvia \
--to=pablo@netfilter.org \
--cc=arnd@arndb.de \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--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.