[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1447119071-19392-1-git-send-email-palmer@dabbelt.com>
Date: Mon, 9 Nov 2015 17:30:57 -0800
From: Palmer Dabbelt <palmer@...belt.com>
To: peterz@...radead.org
Cc: x86@...nel.org
Subject: [PATCH v5] Remove #ifdef CONFIG_* from all userspace headers
I think this should _actually_ be ready to go this time, the buildbot found
some errors in arches that I didn't test for.
Changes since v4 (<1446579994-9937-1-git-send-email-palmer@...belt.com>)
* #9 was changed to work on arm by moving the enum to an in-kernel header
file.
* #13 was added, this fixes a problem on blackfin.
Changes since v3 (<1442271047-4908-1-git-send-email-palmer@...belt.com>)
* #4 is very different: rather than defining a canonical value for
MAP_UNINITIALIZED, it just punts on the problem and lets arch maintainers
deal with it. There's still an #ifndef MAP_UNINITIALIZED in there, but that
shouldn't get triggered by anything because the arch headers should set it
to whatever they actually want.
* #11 defines MAX_RAW_MINORS to 2^20 instead of 2^16.
* #13 moves the variable around a bit so it gets initialized. I forgot I was
in perl and not C :).
Changes since v2 (<1441832902-28993-1-git-send-email-palmer@...belt.com>)
* Patch set renamed.
* #2 is rewritten to use sys_ni.c instead of an #ifdef
* #3, #6, #8, #9, #10, and #11 no longer use "#ifdef __KERNEL__" but
have instead moved the offending lines to the correct, kernel-only
files.
* #4 has been rewritten to always define MAP_UNINITIALIZED to
non-zero, rather than defining it to zero when in userspace.
* #5 got a whole lot longer -- rather than just always hiding these
fields from userspace, there is now a second "struct
elf_fdpic_prstatus" structure. This should allow userspace to
parse core dumps correctly.
* Rebased onto 9c488de24f7264f08d341024bffdd637b4d04c96.
Changes since v1 (<1441152610-22566-1-git-send-email-palmer@...belt.com>)
* All patches but #1 were added.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists