SO_RXQ_ALLOC: use a non-sequential sockopt number to avoid conflicts.

It's unsafe to just use the next sockopt in the sequence, because kernel
updates from upstream are likely to use that one.  In fact, the upcoming
cherry-pick does exactly that.

Change-Id: I95783b1e0878e0bc345d653dc1247a275c1a5675
diff --git a/arch/arm/include/asm/socket.h b/arch/arm/include/asm/socket.h
index 23061f7..3ff6501 100644
--- a/arch/arm/include/asm/socket.h
+++ b/arch/arm/include/asm/socket.h
@@ -61,6 +61,6 @@
 #define SO_DOMAIN		39
 
 #define SO_RXQ_OVFL             40
-#define SO_RXQ_ALLOC		41
+#define SO_RXQ_ALLOC		101  /* non-upstreamed sockopt */
 
 #endif /* _ASM_SOCKET_H */
diff --git a/include/asm-generic/socket.h b/include/asm-generic/socket.h
index 56d2b13..8e7c2f7 100644
--- a/include/asm-generic/socket.h
+++ b/include/asm-generic/socket.h
@@ -64,5 +64,6 @@
 #define SO_DOMAIN		39
 
 #define SO_RXQ_OVFL             40
-#define SO_RXQ_ALLOC		41
+#define SO_RXQ_ALLOC		101  /* non-upstreamed sockopt */
+
 #endif /* __ASM_GENERIC_SOCKET_H */