summaryrefslogtreecommitdiff
path: root/crypto/xts.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-02-26 11:25:04 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2023-02-26 11:25:04 -0800
commitd4563201f33a022fc0353033d9dfeb1606a88330 (patch)
treead154b7ba6dcbafb4b71e62ea1240f045edbacb6 /crypto/xts.c
parent2fcd07b7ccd5fd10b2120d298363e4e6c53ccf9c (diff)
downloadlwn-d4563201f33a022fc0353033d9dfeb1606a88330.tar.gz
lwn-d4563201f33a022fc0353033d9dfeb1606a88330.zip
Documentation: simplify and clarify DCO contribution example language
Long long ago, in a more innocent time, Greg wrote the clarification for how the DCO should work and that you couldn't make anonymous contributions, because the sign-off needed to be something we could check back with. It was 2006, and nobody reacted to the wording, the whole Facebook 'real name' controversy was a decade in the future, and nobody even thought about it. And despite the language, we've always accepted nicknames and that language was never meant to be any kind of exclusionary wording. In fact, even when it became a discussion in other adjacent projects, apparently nobody even thought to just clarify the language in the kernel docs, and instead we had projects like the CNCF that had long discussions about it, and wrote their own clarifications [1] of it. Just simplify the wording to the point where it shouldn't be causing unnecessary angst and pain, or scare away people who go by preferred naming. Link: https://github.com/cncf/foundation/blob/659fd32c86dc/dco-guidelines.md [1] Fixes: af45f32d25cc ("We can not allow anonymous contributions to the kernel") Acked-by: Greg KH <gregkh@linuxfoundation.org> Acked-by: Michael Dolan <mdolan@linuxfoundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto/xts.c')
0 files changed, 0 insertions, 0 deletions