nitter.vloup.ch/paxteam/status/8… so an incomplete commit that explicitly mentions it hasn't yet been fully ported from PaX is a problem?
This tweet is unavailable
2
4
1
did you publish copyrighted code attributing it to yourself and not its copyright owner or not? really simple question.
1
It says there that it's in the process of being ported from PaX. That's more credit than you give to people.
1
you're not answering the question. do you feel guilty of copyright violation? you should be, and it's not the only commit.
1
Nope, do not feel guilty of any copyright violation. Haven't made any claims about being the original author of this code.
2
1
you have, check who git thinks the author of that code is. it's explicitly called out in the kernel's DCO too.
1
This is not mainline. The __ro_after_init changes submitted upstream clearly say that they are extracted from the PaX patches.
2
Replying to @CopperheadOS
copyright law doesn't care if it's called 'mainline' or not, you still cannot violate the law.

Jun 4, 2017 · 3:07 PM UTC

1
Replying to @paxteam
There's no violation of the law. The Linux kernel contribution guidelines are not a legal code.
1
Three lines (that's literally what you are complaining about) of __ro_after_init changes are not copyrightable in the US / Canada anyway.
1
4