asm/unaligned.h doesn't work well as the very first include
Subsystems (3)
PATCH 1/1 asm/unaligned.h doesn't work well as the very first include
--- net/mac80211/mesh.h | 1 + net/mac80211/mesh_hwmp.c | 1 - 2 files changed, 1 insertions(+), 1 deletions(-)
net/mac80211/mesh.h +1 -0
@@ -13,6 +13,7 @@#include <linux/types.h> #include <linux/jhash.h> +#include <asm/unaligned.h> #include "ieee80211_i.h"
net/mac80211/mesh_hwmp.c +0 -1
@@ -7,7 +7,6 @@* published by the Free Software Foundation. */ -#include <asm/unaligned.h> #include "mesh.h" #define TEST_FRAME_LEN 8192
Signature · 1 line
1.5.3.GIT
David Miller
maintainerFrom: Al Viro <[email protected]>
Date: Sun, 27 Apr 2008 06:19:18 +0100
Quoted 1 line
Signed-off-by Al Viro <[email protected]>
Patch applied, thanks a lot Al.
Quoted 23 lines · Al Viro
Signed-off-by Al Viro <[email protected]>--- net/mac80211/mesh.h | 1 + net/mac80211/mesh_hwmp.c | 1 - 2 files changed, 1 insertions(+), 1 deletions(-)net/mac80211/mesh.h +1
-0@@ -13,6 +13,7 @@#include <linux/types.h> #include <linux/jhash.h> +#include <asm/unaligned.h> #include "ieee80211_i.h" net/mac80211/mesh_hwmp.c +0
-0
net/mac80211/mesh_hwmp.c line 10
Quoted 5 lines
net/mac80211/mesh_hwmp.c +0
-1@@ -7,7 +7,6 @@* published by the Free Software Foundation. */ -#include <asm/unaligned.h> #include "mesh.h"
It has been discussed that any .h file should pull in what it needs so the other of includes does not matter. Some do them alphabetically.
Why not fix asm-*/unaligned.h so all users now and future are fixed in one shot?
Sam
Quoted 3 lines · Sam Ravnborg
It has been discussed that any .h file should pull in what it needs so the other of includes does not matter. Some do them alphabetically.
It has been discussed or it has been agreed? IMO it's a bullshit - especially for low-level stuff like that.
As for the way some do includes... It's not exactly a family-friendly list, but still I'd rather not comment in details on the existing practices...
Quoted 11 lines · Al Viro
Quoted 3 lines · Sam Ravnborg
It has been discussed that any .h file should pull in what it needs so the other of includes does not matter. Some do them alphabetically.
It has been discussed or it has been agreed? IMO it's a bullshit - especially for low-level stuff like that.
As for the way some do includes... It's not exactly a family-friendly list, but still I'd rather not comment in details on the existing practices...
I'm redoing the unaligned handling in -mm at the moment, and it avoids this problem.
Harvey