remove warm reboot from diagnostic target

Initially the diagnostic target was only tied to one type of system
event. This one system event required a warm reboot so it made sense to
just put that directly in this recipe. There are now new use cases for
the diagnostic target that do not want or need a warm reboot.

Remove the warm reboot from the diagnostic target and let other recipes
add it if needed for their use cases.

Tested:
- Verified with all commits in this Topic that the witherspoon system
  has the same service layout as before and the rainier system
  has the new layout (crash used for mpipl)

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I31cf0c9a4149a09d7e3f6a4d6b099fc369a0958c
1 file changed
tree: ec0968ab1b8b9576db7dc5c5ed6af665f1b453b0
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.