Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Balazs Scheidler <bazsi77@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v2] netfilter: nft_socket: add wildcard support
Date: Sat, 29 Aug 2020 13:07:33 +0200	[thread overview]
Message-ID: <20200829110733.GA24324@salvia> (raw)
In-Reply-To: <20200829061915.21634-1-bazsi77@gmail.com>

On Sat, Aug 29, 2020 at 08:19:15AM +0200, Balazs Scheidler wrote:
> Add NFT_SOCKET_WILDCARD to match to wildcard socket listener.

Applied, thanks Balazs.

> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> Signed-off-by: Balazs Scheidler <bazsi77@gmail.com>
> ---
> @Pablo: this contains the enum addition as well as the explicit check for IPv6

Thanks, hopefully this is fixing up the kbuild robot report.

      reply	other threads:[~2020-08-29 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 15:44 [PATCH nf-next] netfilter: nft_socket: add wildcard support Pablo Neira Ayuso
2020-08-28 19:55 ` kernel test robot
2020-08-28 19:59 ` kernel test robot
2020-08-29  6:19 ` [PATCH nf-next v2] " Balazs Scheidler
2020-08-29 11: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=20200829110733.GA24324@salvia \
    --to=pablo@netfilter.org \
    --cc=bazsi77@gmail.com \
    --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