From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: Rebasing nf-next
Date: Tue, 6 Dec 2016 21:57:37 +0100 [thread overview]
Message-ID: <20161206205737.GA22832@salvia> (raw)
Hi,
In order to reduce the (already large) batch that I'm going to pass to
David, I'm rebasing nf-next to squash patches that fix bugs,
compilation warnings and other fallout from ongoing development. List
of patches that I have squashed into master patch are:
* netfilter: nf_tables: silence gcc warning with stateful object maps
* netfilter: nf_tables: restore check for NFTA_SET_ELEM_LIST_ELEMENTS
* netfilter: nft_counter: move counter reset into separated function
* netfilter: nft_quota: don't read quota twice on reset
* netfilter: add list element test to br_netfilter_hooks
* netfilter: fix build failure with CONNTRACK=n NF_DEFRAG=y
* netfilter: nft_payload: restrict l4 checksum updates to l3 header mangling
Sorry.
next reply other threads:[~2016-12-06 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 20:57 Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-28 19:10 rebasing nf-next Pablo Neira Ayuso
2020-03-12 13:43 Pablo Neira Ayuso
2019-07-03 19:16 Rebasing nf-next Pablo Neira Ayuso
2018-01-08 15:45 Pablo Neira Ayuso
2016-11-01 19:37 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=20161206205737.GA22832@salvia \
--to=pablo@netfilter.org \
--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 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).