From: Gargi Sharma <gs051095@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: pablo@netfilter.orgm, outreachy-kernel@googlegroups.com,
Gargi Sharma <gs051095@gmail.com>
Subject: [PATCH 3/4] extensions: libebt_mark: Constify option struct
Date: Tue, 28 Mar 2017 00:15:29 +0530 [thread overview]
Message-ID: <a95fb3da52de09e103736a49b838b78f091a3460.1490640256.git.gs051095@gmail.com> (raw)
In-Reply-To: <cover.1490640256.git.gs051095@gmail.com>
In-Reply-To: <cover.1490640256.git.gs051095@gmail.com>
The struct brmark_opts of the type option is only
used to initialise the extra_opts field in xtables_target
struct and is no modified anywhere.
Signed-off-by: Gargi Sharma <gs051095@gmail.com>
---
extensions/libebt_mark.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/extensions/libebt_mark.c b/extensions/libebt_mark.c
index a1a208c..7b80b22 100644
--- a/extensions/libebt_mark.c
+++ b/extensions/libebt_mark.c
@@ -25,7 +25,7 @@ static int mark_supplied;
#define MARK_ORMARK '3'
#define MARK_ANDMARK '4'
#define MARK_XORMARK '5'
-static struct option brmark_opts[] = {
+static const struct option brmark_opts[] = {
{ .name = "mark-target",.has_arg = true, .val = MARK_TARGET },
/* an oldtime messup, we should have always used the scheme
* <extension-name>-<option> */
--
2.7.4
next prev parent reply other threads:[~2017-03-27 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 18:45 [PATCH 0/4] Constify option structures Gargi Sharma
2017-03-27 18:45 ` [PATCH 1/4] extensions: libebt_limit: Constify option struct Gargi Sharma
2017-03-27 18:45 ` [PATCH 2/4] extenstions: libebt_mark_m: " Gargi Sharma
2017-03-27 18:45 ` Gargi Sharma [this message]
2017-03-27 18:45 ` [PATCH 4/4] extensions: libebt_nflog: " Gargi Sharma
2017-03-27 18:49 ` [Outreachy kernel] [PATCH 0/4] Constify option structures 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=a95fb3da52de09e103736a49b838b78f091a3460.1490640256.git.gs051095@gmail.com \
--to=gs051095@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pablo@netfilter.orgm \
/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).