When fixing a kernel configuration warning, it is often necessary to
modify the kernel's meta-data and re-run the tools to update and
re-audit the config. This implies that the patch, config and audit
steps are run multiple times.

The tools had a bug that would incorrectly restore old meta-data
versus using updated configuration. Updating the kern-tools SRCREV
to fix the issue.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Update the SRCREV for the following incremental improvement in patch
processing time:

    kgit-meta: skip patches on non-leaf nodes

    In a similar way as commit 0768d697 [kgit-meta: dont run kgit-s2q
    for
    non-leaf nodes], we can save even more processing time by not even
    analysing and linking patches if we aren't on the leaf node of the
    tree.

    This early exit can save nearly 95% of the time required to "patch"
    a tree when no changes are actually applied.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

After a linux-yocto style kernel is configured, a kernel configuration
audit is executed to detect common errors or issues with the config.

This output used to be visible, but was made less obvious to not alarm
users unnecessarily (since some configuration issues are acceptable).

There are some classes of configuration issue that are worth being
visible, and that is specified configuration values that do not make the
final .config. These dropped options can result in any number of runtime
failures, so flagging them at build time makes sense.

The visibility of auditing is controlled by KCONF_AUDIT_LEVEL:

   0: no reporting
   1: report options that are specified, but not in the final config
   2: report options that are not hardware related, but set by a BSP

The default level is 1, with level 2 and above being for BSP development
only.

If these conditions are detected, warnings will be generated as follows:

  WARNING: [kernel config]: specified values did not make it into the
  kernel's final configuration:

  Value requested for CONFIG_SND_PCSP not in final ".config"
  Requested value: "CONFIG_SND_PCSP=y"
  Actual value set: ""

or

  WARNING: [kernel config]: BSP specified non-hw configuration:

  CONFIG_BLOCK
  CONFIG_CFG80211_WEXT
  CONFIG_CORDIC
  CONFIG_CRC8
  CONFIG_EFIVAR_FS
  CONFIG_EFI_PARTITION
  CONFIG_NET
  CONFIG_NETDEVICES
  CONFIG_PARTITION_ADVANCED
  CONFIG_WEXT_CORE
  CONFIG_WEXT_PROC
  CONFIG_WIRELESS

At this point thse are only a warnings, since there needs to be time for
layers and configuration fragments to be validated against this new
check.

[YOCTO: #6943]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Updating the SRCREV to import the following kern-tools patch:

    kgit-meta: always clear series file on branch transitions

This was triggered by the patch optimization changes, that no longer
run do_patch if a leaf/final branch is not being processed.

Without this change, invalid patches, or already applied patches in
an existig series file will be re-used which leads to missing files,
or patch errors.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

Updating the SRCREV for the following commits:

  4822d22b65c2 kgit-meta: dont run kgit-s2q for non-leaf nodes
  3e3de1b9cdec createme: remove meta branch checks

With these, we save 10 seconds on the average patch phase, and
significantly more if very long patch queues are used.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

During patch processing a consolidated set of configs, patches and directives
is created under the kernel source tree being modified. During that processing,
absolutely paths are converted to relative. It has been found that if directories
are sufficiently similar, like so:

  /path/to/my-linux
  /path/to/my-linux-3.16

The processing will chop to much of some paths, resulting in invalid relative
directories (like -3.16 in the above example).

Importing the following two kern tools fixes for the issue:

  23345b8846fe kgit: retain trailing / in directory processing
  a8cf93a3bc94 kgit-s2q: move subject and diffstat mismatch to 'fuzzy' matching

[YOCTO: #6753]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

From the kern-tools commit:

    tools: allow meta directories that are not the same as the branch name

    With this change it is now possible to have a meta branch with meta data
    in a directory that is not the same name as the branch.

    The changes to three parts of the build are required to discover the name
    of the meta directory by relying on the fact that in a clean/proper build
    the meta directory is the only untracked, top level directory in the build.

    As such, we can restore a checkpoint and then examine the build directory
    to determine the meta directory name .. avoiding any new variables to
    indicate this to the scripts and build system.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

In order to generate and support kernel trees with full history, we need
to modify the kernel tools

 e914d570232a kgit-checkpoint: ensure that full meta-data artifacts are maintained
 192be836d318 kgit-scc: allow meta-data history to be maintained

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

A lot of our recipes had short one-line DESCRIPTION values and no
SUMMARY value set. In this case it's much better to just set SUMMARY
since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY
is at least useful. I also took the opportunity to fix up a lot of the
new SUMMARY values, making them concisely explain the function of the
recipe / package where possible.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>

Updating the kern-tools SRCREV to import the following change:

    kgit-s2q: always update ORIG_HEAD after applying changes

    In situations where git am fails to apply patches, and git apply is used,
    we must update ORIG_HEAD as well as HEAD. This is required, since if the
    next patch in the queue also fails git am application, it will reset to
    ORIG_HEAD before using git apply. If we haven't updated ORIG_HEAD, we'll
    end up warping back to the top of the branch each time.

This problem can only be seen in very specific situations, in particular if
a generated BSP branches from qemuppc, and has a series of non git "am able"
patches. We fail, since all of the qemuppc patches are not applied due to
the branch head constantly being reset.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>