Netdev List
 help / color / mirror / Atom feed
From: Daniel Baluta <dbaluta@ixiacom.com>
To: willemb@google.com, edumazet@google.com, davem@davemloft.net,
	netdev@vger.kernel.org
Cc: Daniel Baluta <dbaluta@ixiacom.com>
Subject: [PATCH net-next] packet: Fix compile error
Date: Wed, 20 Mar 2013 00:01:21 +0200	[thread overview]
Message-ID: <1363730481-7168-1-git-send-email-dbaluta@ixiacom.com> (raw)

PACKET_FANOUT_ROLLOVER and PACKET_FANOUT_FLAG_ROLLOVER are not declared in
<tree>/usr/include/linux/if_packet.h together with the other PACKET_FANOUT_* macros
as one would expect. This causes the following compilation error:
<snip>
psock_fanout.c: In function ‘test_control_single’:
psock_fanout.c:230:23: error: ‘PACKET_FANOUT_ROLLOVER’ undeclared (first use in this function)
</snip>

Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
---
 .../testing/selftests/net-afpacket/psock_fanout.c  |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/net-afpacket/psock_fanout.c b/tools/testing/selftests/net-afpacket/psock_fanout.c
index 09dbf93..c827415 100644
--- a/tools/testing/selftests/net-afpacket/psock_fanout.c
+++ b/tools/testing/selftests/net-afpacket/psock_fanout.c
@@ -63,6 +63,7 @@
 #define PACKET_FANOUT_LB		1
 #define PACKET_FANOUT_CPU		2
 #define PACKET_FANOUT_FLAG_DEFRAG	0x8000
+#endif
 
 #ifndef PACKET_FANOUT_ROLLOVER
 #define PACKET_FANOUT_ROLLOVER		3
@@ -72,8 +73,6 @@
 #define PACKET_FANOUT_FLAG_ROLLOVER	0x1000
 #endif
 
-#endif
-
 #define DATA_LEN			100
 #define DATA_CHAR			'a'
 
-- 
1.7.5.4

             reply	other threads:[~2013-03-19 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 22:01 Daniel Baluta [this message]
2013-03-19 22:07 ` [PATCH net-next] packet: Fix compile error David Miller
2013-03-19 22:46   ` Daniel Baluta
2013-03-19 23:06     ` David Miller

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=1363730481-7168-1-git-send-email-dbaluta@ixiacom.com \
    --to=dbaluta@ixiacom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    /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