From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/2] Two non-functional fixes for nft_set_pipapo
Date: Tue, 18 Feb 2020 22:07:43 +0100 [thread overview]
Message-ID: <20200218210743.2tuya2wnryirf4o7@salvia> (raw)
In-Reply-To: <cover.1581699548.git.sbrivio@redhat.com>
On Fri, Feb 14, 2020 at 06:14:12PM +0100, Stefano Brivio wrote:
> Patch 1/2 fixes examples of mapping table values in comments,
> patch 2/2 drops an abuse of unlikely(), both reported by Pablo.
>
> No functional changes are intended here. I'm not entirely sure
> these should be for nf-next, but I guess so as they don't carry
> any functional fix.
Applied this fixes to nf.git. Thanks.
prev parent reply other threads:[~2020-02-18 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:14 [PATCH nf-next 0/2] Two non-functional fixes for nft_set_pipapo Stefano Brivio
2020-02-14 17:14 ` [PATCH nf-next 1/2] netfilter: nft_set_pipapo: Fix mapping table example in comments Stefano Brivio
2020-02-14 17:14 ` [PATCH nf-next 2/2] netfilter: nft_set_pipapo: Don't abuse unlikely() in pipapo_refill() Stefano Brivio
2020-02-14 17:33 ` [PATCH nf-next 0/2] Two non-functional fixes for nft_set_pipapo Pablo Neira Ayuso
2020-02-18 21:07 ` Pablo Neira Ayuso [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=20200218210743.2tuya2wnryirf4o7@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sbrivio@redhat.com \
/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).