Bug 10967
Summary: | include/asm-i386 removed but not documented | ||
---|---|---|---|
Product: | Documentation | Reporter: | Royce Souther (osgnuru) |
Component: | man-pages | Assignee: | Roland Kletzing (devzero) |
Status: | CLOSED INVALID | ||
Severity: | normal | CC: | devzero |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24+ | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Royce Souther
2008-06-23 09:52:42 UTC
>Problem Description:Between kernel 2.6.23.17 and 2.6.24 the include/asm-i386 >directory was removed it`s because of i386/x64 unification. see http://lwn.net/Articles/243704/ >there is no mention of it in the change log or the documentation. it`s all documented - it began here http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=96a388de5dc53a8b234b3fd41f3ae2cedc9ffd42 and this is the latest information about those changes in asm-i386 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=include/asm-x86;h=9999ac87466fcbe63aa527c61f1e11627a349dea;hb=481c5346d0981940ee63037eb53e4e37b0735c10 git provides more detail than any documentation can provide. it`s the whole changelog for the kernel - patch by patch. >There are still many source files that include headers from asm-i386 which ? >and also third party software that will try to include /usr/include/asm-i386 >>will now be broken for anyone trying to compile a kernel on a 32 bit CPU. yes, we know out of tree code is a pain in the ass - but it`s like that - and that`s the way it is. see http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/stable_api_nonsense.txt Would have been nice to see a one liner about this change in the change log. Not trying to be a jerk. I know trying to document everything can be a big job. Two thumbs up for all the kernel developers and the work they are doing. Thanks. you`re welcome
>Would have been nice to see a one liner about this change in the change log.
ok, but this is really not the best place for discussing this. if there is something to improve or to criticize, this should be better brought up on lkml please.
|