All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: rfc: netfilter: Unhide FWINV macro arguments ?
Date: Fri, 17 Jun 2016 08:41:59 -0700	[thread overview]
Message-ID: <1466178119.19647.110.camel@perches.com> (raw)
In-Reply-To: <20160617115932.GA5482@salvia>

On Fri, 2016-06-17 at 13:59 +0200, Pablo Neira Ayuso wrote:
> On Thu, Jun 16, 2016 at 11:20:59AM -0700, Joe Perches wrote:
> > There are several FWINV #defines with identical form
> > that hide a specific structure variable and dereference
> > it with a invflags member.
> Right, this macro is obscure indeed.
[]
> I'll be taking a patch to sort out this. Thanks.

I'll wait until you pick up or reject the
ether_addr_equal_masked patch as that changes
a few FWINV uses.

      reply	other threads:[~2016-06-17 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 18:20 rfc: netfilter: Unhide FWINV macro arguments ? Joe Perches
2016-06-17 11:59 ` Pablo Neira Ayuso
2016-06-17 15:41   ` Joe Perches [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=1466178119.19647.110.camel@perches.com \
    --to=joe@perches.com \
    --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 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.