On Tue, Feb 17, 2015 at 01:02:50AM +0100, Jan Engelhardt wrote:
> On Tuesday 2015-02-17 00:05, Mikko Rapeli wrote:
>
> >Fixes userspace compilation errors like:
> >
> >error: field ‘in’ has incomplete type
> >struct in_addr in;
> >
> >+#include
>
> Patch 36/45 included linux/in.h instead of
On Tue, Feb 17, 2015 at 01:02:50AM +0100, Jan Engelhardt wrote:
On Tuesday 2015-02-17 00:05, Mikko Rapeli wrote:
Fixes userspace compilation errors like:
error: field ‘in’ has incomplete type
struct in_addr in;
+#include linux/if.h
Patch 36/45 included linux/in.h instead of
On Tuesday 2015-02-17 00:05, Mikko Rapeli wrote:
>Fixes userspace compilation errors like:
>
>error: field ‘in’ has incomplete type
>struct in_addr in;
>
>+#include
Patch 36/45 included linux/in.h instead of linux/if.h for addressing "in has
incomplete
type". Should this be used here too?
--
Fixes userspace compilation errors like:
error: field ‘in’ has incomplete type
struct in_addr in;
Signed-off-by: Mikko Rapeli
---
include/uapi/linux/netfilter_bridge.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/netfilter_bridge.h
Fixes userspace compilation errors like:
error: field ‘in’ has incomplete type
struct in_addr in;
Signed-off-by: Mikko Rapeli mikko.rap...@iki.fi
---
include/uapi/linux/netfilter_bridge.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/netfilter_bridge.h
On Tuesday 2015-02-17 00:05, Mikko Rapeli wrote:
Fixes userspace compilation errors like:
error: field ‘in’ has incomplete type
struct in_addr in;
+#include linux/if.h
Patch 36/45 included linux/in.h instead of linux/if.h for addressing in has
incomplete
type. Should this be used here too?
6 matches
Mail list logo
