summaryrefslogtreecommitdiffstats
path: root/lib/interval_tree.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2018-08-18 21:19:56 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2018-08-18 21:19:56 +0200
commit771c035372a036f83353eef46dbb829780330234 (patch)
treead508b447984cee53096cdd078158c47d0cd206c /lib/interval_tree.c
parentMerge tag 'driver-core-4.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel... (diff)
downloadlinux-771c035372a036f83353eef46dbb829780330234.tar.xz
linux-771c035372a036f83353eef46dbb829780330234.zip
deprecate the '__deprecated' attribute warnings entirely and for good
We haven't had lots of deprecation warnings lately, but the rdma use of it made them flare up again. They are not useful. They annoy everybody, and nobody ever does anything about them, because it's always "somebody elses problem". And when people start thinking that warnings are normal, they stop looking at them, and the real warnings that mean something go unnoticed. If you want to get rid of a function, just get rid of it. Convert every user to the new world order. And if you can't do that, then don't annoy everybody else with your marking that says "I couldn't be bothered to fix this, so I'll just spam everybody elses build logs with warnings about my laziness". Make a kernelnewbies wiki page about things that could be cleaned up, write a blog post about it, or talk to people on the mailing lists. But don't add warnings to the kernel build about cleanup that you think should happen but you aren't doing yourself. Don't. Just don't. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/interval_tree.c')
0 files changed, 0 insertions, 0 deletions