summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-05-11 03:04:04 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2023-05-11 03:04:04 +0200
commit80e62bc8487b049696e67ad133c503bf7f6806f7 (patch)
tree978c16fb68d8f24b01c4f53037d4659bb5cfc163 /drivers
parentMerge tag 'fsnotify_for_v6.4-rc2' of git://git.kernel.org/pub/scm/linux/kerne... (diff)
downloadlinux-80e62bc8487b049696e67ad133c503bf7f6806f7.tar.xz
linux-80e62bc8487b049696e67ad133c503bf7f6806f7.zip
MAINTAINERS: re-sort all entries and fields
It's been a few years since we've sorted this thing, and the end result is that we've added MAINTAINERS entries in the wrong order, and a number of entries have their fields in non-canonical order too. So roll this boulder up the hill one more time by re-running ./scripts/parse-maintainers.pl --order on it. This file ends up being fairly painful for merge conflicts even normally, since unlike almost all other kernel files it's one of those "everybody touches the same thing", and re-ordering all entries is only going to make that worse. But the alternative is to never do it at all, and just let it all rot.. The rc2 week is likely the quietest and least painful time to do this. Requested-by: Randy Dunlap <rdunlap@infradead.org> Requested-by: Joe Perches <joe@perches.com> # "Please use --order" Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions