Skip to contentSkip to conversation

byteorder: add new headers for make headers-install

PATCH In review Harvey Harrison 2 participants 3 messages Aug 18, 2008 – Aug 20, 2008

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 byteorder: add new headers for make headers-install

---
Andrew, two fixes before the arches start moving over.

 include/linux/Kbuild |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
include/linux/Kbuild +2 -0
index 7d97067..0ffee42 100644
@@ -179,6 +179,7 @@ unifdef-y += audit.h
 unifdef-y += auto_fs.h
 unifdef-y += auxvec.h
 unifdef-y += binfmts.h
+unifdef-y += byteorder.h
 unifdef-y += capability.h
 unifdef-y += capi.h
 unifdef-y += cciss_ioctl.h
@@ -335,6 +336,7 @@ unifdef-y += soundcard.h
 unifdef-y += stat.h
 unifdef-y += stddef.h
 unifdef-y += string.h
+unifdef-y += swab.h
 unifdef-y += synclink.h
 unifdef-y += sysctl.h
 unifdef-y += tcp.h
Signature · 1 line
1.6.0.274.g8aacc
#1 lore raw
Quoted 3 lines · Harvey Harrison

---
Andrew, two fixes before the arches start moving over.

We don't expose cpu_to_le32() et al., do we? Only __cpu_to_le32() and similar? Which exported headers use these -- and are they actually using the __ versions? If not, they're not going to work anyway, are they?

Signature · 2 lines
David Woodhouse                            Open Source Technology Centre
[email protected]                              Intel Corporation
#2 lore raw
Quoted 9 lines · David Woodhouse
Quoted 3 lines · Harvey Harrison

---
Andrew, two fixes before the arches start moving over.

We don't expose cpu_to_le32() et al., do we? Only __cpu_to_le32() and similar? Which exported headers use these -- and are they actually using the __ versions? If not, they're not going to work anyway, are they?

Correct, the cpu_to_le32(), etc are wrapped in #ifdef KERNEL, but this adds the export for the two new headers that will replace the byteorder/*.h implementation.

Once each arch has moved over, include/linux/byteorder/* will go away.

Cheers,

Harvey