From: Eric Engestrom <eric.engestrom@imgtec.com>
To: <linux-kernel@vger.kernel.org>
Cc: Eric Engestrom <eric@engestrom.ch>,
Eric Engestrom <eric.engestrom@imgtec.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
<netfilter-devel@vger.kernel.org>, <coreteam@netfilter.org>
Subject: [PATCH 2/2] netfilter: add missing macro
Date: Fri, 8 Jul 2016 17:29:11 +0100 [thread overview]
Message-ID: <20160708162911.18756-2-eric.engestrom@imgtec.com> (raw)
In-Reply-To: <20160708162911.18756-1-eric.engestrom@imgtec.com>
Signed-off-by: Eric Engestrom <eric.engestrom@imgtec.com>
---
This can't compile without this macro… Is this header really used by anyone?
Should it be removed, to avoid bit-rot?
---
include/uapi/linux/netfilter/xt_sctp.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/uapi/linux/netfilter/xt_sctp.h b/include/uapi/linux/netfilter/xt_sctp.h
index 58ffcfb..e4410db 100644
--- a/include/uapi/linux/netfilter/xt_sctp.h
+++ b/include/uapi/linux/netfilter/xt_sctp.h
@@ -3,6 +3,8 @@
#include <linux/types.h>
+#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof(arr)[0])
+
#define XT_SCTP_SRC_PORTS 0x01
#define XT_SCTP_DEST_PORTS 0x02
#define XT_SCTP_CHUNK_TYPES 0x04
--
2.9.0
next prev parent reply other threads:[~2016-07-08 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 16:29 [PATCH 1/2] libnvdimm: add missing macros Eric Engestrom
2016-07-08 16:29 ` Eric Engestrom
2016-07-08 16:29 ` Eric Engestrom [this message]
2016-07-08 17:00 ` [PATCH 2/2] netfilter: add missing macro kbuild test robot
2016-07-11 10:41 ` Pablo Neira Ayuso
2016-07-11 10:41 ` Pablo Neira Ayuso
2016-07-08 17:25 ` [PATCH 1/2] libnvdimm: add missing macros kbuild test robot
2016-07-08 17:25 ` kbuild test robot
2016-07-08 19:32 ` Dan Williams
2016-07-08 19:32 ` Dan Williams
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=20160708162911.18756-2-eric.engestrom@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=coreteam@netfilter.org \
--cc=eric@engestrom.ch \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@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.