RFC KABI example conversion and cleanup
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 78 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Create initial kernel ABI header infrastructureMakefile include/ include/ +21 more | +188 | 20 replies | |
| 2/2 | Generalize fd_set handling across architecturesinclude/ include/ include/ +22 more | +112 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/2] KABI example conversion and cleanup
Quoted 2 lines · On Fri, 24 Mar 2006 17:46:27 -0500 Kyle Moffett <[email protected]> wrote:
I'm working on some sample patches now which I'll try to post in a few days if I get the time.
Ok, here's a sample of the KABI conversion and cleanup patches that I'm proposing. I have a few fundamental goals for these patches:
1) The Linux kernel compiles and works at every step along the way
2) Since most of the headers are currently quite broken with respect to GLIBC and userspace, I won't spend much extra time preserving compatibility with GLIBC, userspace, or non-GCC compilers.
3) Everything in include/kabi will have a __kabi_ or __KABI_ prefix.
4) Headers in include/linux that need the KABI interfaces will include the corresponding <kabi/*.h> header and define or typedef the necessary KABI definitions to the names the kernel wants.
5) The stuff in include/kabi/*.h should always be completely independent of userspace/kernelspace and not require any includes outside of <kabi/*>. This means that the only preprocessor symbols that we can assume are present are those provided by the compiler itself.
Cheers,
Kyle Moffett