From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Netfilter/IPVS fixes for net
Date: Sat, 02 Aug 2014 16:49:46 -0700 (PDT) [thread overview]
Message-ID: <20140802.164946.1059611435908084703.davem@davemloft.net> (raw)
In-Reply-To: <1406911239-6250-1-git-send-email-pablo@netfilter.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Fri, 1 Aug 2014 18:40:36 +0200
> The following patchset contains Netfilter/IPVS fixes for your net tree,
> they are:
>
> 1) Maintain all DSCP and ECN bits for IPv6 tun forwarding. This
> resolves an inconsistency between IPv4 and IPv6 behaviour.
> Patch from Alex Gartrell via Simon Horman.
>
> 2) Fix unnoticeable blink in xt_LED when the led-always-blink option is
> used, from Jiri Prchal.
>
> 3) Add missing return in nft_del_setelem(), otherwise this results in a
> double call of nft_data_uninit() in the nf_tables code, from Thomas Graf.
>
> You can pull these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git
Pulled, thanks Pablo.
next prev parent reply other threads:[~2014-08-02 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 16:40 [PATCH 0/3] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2014-08-01 16:40 ` [PATCH 1/3] ipvs: Maintain all DSCP and ECN bits for ipv6 tun forwarding Pablo Neira Ayuso
2014-08-01 16:40 ` [PATCH 2/3] netfilter: xt_LED: fix too short led-always-blink Pablo Neira Ayuso
2014-08-01 16:40 ` [PATCH 3/3] netfilter: nf_tables: Avoid duplicate call to nft_data_uninit() for same key Pablo Neira Ayuso
2014-08-02 23:49 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-13 17:47 [PATCH 0/3] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2019-02-14 0:15 ` 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=20140802.164946.1059611435908084703.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).