From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Subject: [RFC 0/2] typeof keyword, alternate patch
Date: Tue, 30 Jul 2019 16:37:30 +0200 [thread overview]
Message-ID: <20190730143732.2126-1-fw@strlen.de> (raw)
Similar idea to Pablos approach, similar drawbacks.
It can be used
First patch is to make it easier to later on handle concatenations,
maps and the like -- it will retain the proper length so you can
have maps that e.g. return 'ct helper' or 'osf name' values.
Don't know yet when I can work on this again, I will comment
on Pablos patch set soon.
next reply other threads:[~2019-07-30 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 14:37 Florian Westphal [this message]
2019-07-30 14:37 ` [PATCH 1/2] src: store expr, not dtype to track data in sets Florian Westphal
2019-07-31 13:02 ` Pablo Neira Ayuso
2019-07-31 13:10 ` Florian Westphal
2019-07-30 14:37 ` [PATCH 2/2] typeof keyword Florian Westphal
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=20190730143732.2126-1-fw@strlen.de \
--to=fw@strlen.de \
--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).