tree-wide: use __ prefixed gcc attributes (#10843)

As suggest here:

https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax

    "You may optionally specify attribute names with ‘__’ preceding and
    following the name. This allows you to use them in header files without
    being concerned about a possible macro of the same name. For example,
    you may use the attribute name __noreturn__ instead of noreturn. "

(cherry picked from commit 012c2f761bf1eb0b9c784b867293f7f1c17c3080)
6 files changed
tree: 6c1893a5cf15b9de377f2cebc8fffcc58f0fba74
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .mailmap
  7. .mkosi/
  8. .travis.yml
  9. .vimrc
  10. .ycm_extra_conf.py
  11. CODING_STYLE
  12. DISTRO_PORTING
  13. ENVIRONMENT.md
  14. HACKING
  15. LICENSE.GPL2
  16. LICENSE.LGPL2.1
  17. Makefile
  18. NEWS
  19. README
  20. README.md
  21. TODO
  22. TRANSIENT-SETTINGS.md
  23. UIDS-GIDS.md
  24. catalog/
  25. coccinelle/
  26. configure
  27. docs/
  28. factory/etc/
  29. hwdb/
  30. man/
  31. meson.build
  32. meson_options.txt
  33. mkosi.build
  34. modprobe.d/
  35. network/
  36. po/
  37. presets/
  38. rules/
  39. shell-completion/
  40. src/
  41. sysctl.d/
  42. sysusers.d/
  43. test/
  44. tmpfiles.d/
  45. tools/
  46. units/
  47. xorg/
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status
CII Best Practices

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the HACKING file for information how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.