Run oe-stylize on our files

In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.

This commit runs oe-stylize.py on all of our files.  The types of
changes being made can be seen in the commit, but amount to:

1. Setting an explicit key ordering
2. Sectioning the files appropriately
3. Applying rules checking to our files

At some point in the near future, we would turn this on as part of
repotest, but some minor changes need to be upstreamed to meta-oe (WIP)
to make that happen.

Looking for input on whether this is something we'd like to do, and
whether the diffs below look reasonable to folks.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf

1 files changed, 4 insertions, 6 deletions

diff --git a/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-inventory-sel-native.bb b/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-inventory-sel-native.bb
index 4deaf0de17..08ae17d7e2 100644
--- a/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-inventory-sel-native.bb
+++ b/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-inventory-sel-native.bb
@@ -1,21 +1,19 @@
 SUMMARY = "Inventory to Sensor config for non-mrw machines"
-PR = "r1"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10"
-
-inherit phosphor-ipmi-host
-inherit native
-
 PROVIDES += "virtual/phosphor-ipmi-inventory-sel"
+PR = "r1"
 
 SRC_URI += "file://config.yaml"
 
 S = "${WORKDIR}"
 
+inherit phosphor-ipmi-host
+inherit native
+
 do_install() {
         # This recipe would provide the sample inventory to sensor config
         # mapping, for non-mrw machines.
-
         DEST=${D}${sensor_datadir}
         install -d ${DEST}
         install config.yaml ${DEST}/invsensor.yaml