Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / v233-stable
commit314ca2bb5aa1eb761a4e43b6d41e1b2a228c9e17[log] [download]
authorLennart Poettering <lennart@poettering.net>Tue Nov 20 04:34:08 2018 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>Tue Jan 22 20:24:44 2019 +0100
treeb9947937c53546640ff48ef78662a0b481431bdd
parent69765b63f9a2699d9a9387f38c611205e4d7c638 [diff]
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: b9947937c53546640ff48ef78662a0b481431bdd
  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-man.am
  18. Makefile.am
  19. NEWS
  20. README
  21. README.md
  22. TODO
  23. autogen.sh
  24. catalog/
  25. coccinelle/
  26. configure.ac
  27. docs/
  28. factory/etc/
  29. hwdb/
  30. m4/
  31. man/
  32. mkosi.build
  33. mkosi.default ⇨ .mkosi/mkosi.fedora
  34. network/
  35. po/
  36. rules/
  37. shell-completion/
  38. src/
  39. sysctl.d/
  40. system-preset/
  41. sysusers.d/
  42. test/
  43. tmpfiles.d/
  44. tools/
  45. units/
  46. xorg/
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status

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.