Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / e310dd91688c0b6d6eaee9e6889bf61ee6ce09b7
commite310dd91688c0b6d6eaee9e6889bf61ee6ce09b7[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Wed Dec 07 06:55:38 2022 -0600
committerPatrick Williams <patrick@stwcx.xyz>Wed Dec 07 06:55:40 2022 -0600
tree6cc0dbfecf4f329c03bdcaa831a286aeed434914
parent38a1a130c8c35e3819edff61c379f748a63deee2 [diff]
treewide: lint and format

Run all the latest linters and formatters from openbmc-build-scripts.
These were all robotically generated except for fixes due to
markdownlint warnings.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: If16d2fd802a2d452234d8b56b41e79d030138a6b
28 files changed
tree: 6cc0dbfecf4f329c03bdcaa831a286aeed434914
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bbdbg/
  5. bi2cp/
  6. cla-signers/
  7. dbus-pcap/
  8. dbus-top/
  9. dbus-vis/
  10. dbus_sensor_tester/
  11. dbusView/
  12. ddconvnotrunc/
  13. expectedJsonChecker/
  14. format-yaml/
  15. ipkdbg/
  16. netboot/
  17. openbmc-autobump/
  18. openbmctool/
  19. overlay/
  20. pldm/
  21. prepare-emmc-qemu/
  22. pretty-journal/
  23. pwmtachtool/
  24. reboot/
  25. reboot-ping-pong/
  26. rootfs_size/
  27. sensor_yaml_config/
  28. tof-voters/
  29. tracing/
  30. witherspoon-debug/
  31. .linter-ignore
  32. .shellcheck-ignore
  33. LICENSE
  34. OWNERS
  35. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.