From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: [PATCH nft 3/4] main: add missing `OPT_NUMERIC_PROTO` long option.
Date: Tue, 22 Oct 2019 21:58:54 +0100 [thread overview]
Message-ID: <20191022205855.22507-4-jeremy@azazel.net> (raw)
In-Reply-To: <20191022205855.22507-1-jeremy@azazel.net>
The `options` array is missing an entry for `OPT_NUMERIC_PROTO`. Add a
new option, `--numeric-protocol`, consistent with the documentation.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
src/main.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/main.c b/src/main.c
index ebd6d7c322d7..c1c404e14eeb 100644
--- a/src/main.c
+++ b/src/main.c
@@ -116,6 +116,10 @@ static const struct option options[] = {
.name = "numeric-priority",
.val = OPT_NUMERIC_PRIO,
},
+ {
+ .name = "numeric-protocol",
+ .val = OPT_NUMERIC_PROTO,
+ },
{
.name = "numeric-time",
.val = OPT_NUMERIC_TIME,
--
2.23.0
next prev parent reply other threads:[~2019-10-22 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 20:58 [PATCH nft 0/4] Output Flag Fixes Jeremy Sowden
2019-10-22 20:58 ` [PATCH nft 1/4] doc: add missing output flag documentation Jeremy Sowden
2019-10-23 20:36 ` Pablo Neira Ayuso
2019-10-22 20:58 ` [PATCH nft 2/4] py: add missing output flags Jeremy Sowden
2019-10-23 20:38 ` Pablo Neira Ayuso
2019-10-24 9:20 ` Phil Sutter
2019-10-24 9:35 ` Pablo Neira Ayuso
2019-10-24 15:56 ` Phil Sutter
2019-10-24 16:23 ` Pablo Neira Ayuso
2019-10-24 9:14 ` Phil Sutter
2019-10-22 20:58 ` Jeremy Sowden [this message]
2019-10-23 20:42 ` [PATCH nft 3/4] main: add missing `OPT_NUMERIC_PROTO` long option Pablo Neira Ayuso
2019-10-22 20:58 ` [PATCH nft 4/4] main: remove duplicate output flag assignment Jeremy Sowden
2019-10-23 20:42 ` Pablo Neira Ayuso
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=20191022205855.22507-4-jeremy@azazel.net \
--to=jeremy@azazel.net \
--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).