summaryrefslogtreecommitdiffstats
path: root/drivers/spi/omap2_mcspi.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-07-09 19:29:53 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2023-07-09 19:29:53 +0200
commitc192ac7357683f78c2e6d6e75adfcc29deb8c4ae (patch)
tree197598b645a71c99049211112929f5703b5736dd /drivers/spi/omap2_mcspi.c
parentMerge tag 'dma-mapping-6.5-2023-07-09' of git://git.infradead.org/users/hch/d... (diff)
downloadlinux-c192ac7357683f78c2e6d6e75adfcc29deb8c4ae.tar.xz
linux-c192ac7357683f78c2e6d6e75adfcc29deb8c4ae.zip
MAINTAINERS 2: Electric Boogaloo
We just sorted the entries and fields last release, so just out of a perverse sense of curiosity, I decided to see if we can keep things ordered for even just one release. The answer is "No. No we cannot". I suggest that all kernel developers will need weekly training sessions, involving a lot of Big Bird and Sesame Street. And at the yearly maintainer summit, we will all sing the alphabet song together. I doubt I will keep doing this. At some point "perverse sense of curiosity" turns into just a cold dark place filled with sadness and despair. Repeats: 80e62bc8487b ("MAINTAINERS: re-sort all entries and fields") Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/spi/omap2_mcspi.c')
0 files changed, 0 insertions, 0 deletions