python-smart-backend: Remove bogus runtime virtual/

At runtime virtual/ providers make *no* sense at all. They also break debian
packaging since the "/" character is not allowed in debian package names.

This patch removes this runtime provider selection code since it is not
workable and breaks builds.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.0: fix virtio configuration typo

The recent tools updates in master exposed a typo that has existed
in the 3.0 kernel meta data and that breaks the build for boards still
using the 3.0 kernel.

Bumping the meta SRCREV to pickup the following fix:

[
  commit fa9b8c24e84bb9d75d08d197c84c50ce4f99c424
  Author: Bruce Ashfield <bruce.ashfield@windriver.com>
  Date:   Wed Nov 21 09:24:46 2012 -0500

    meta: fix typo in virtio.scc

    virtio.scc was referring to an invalid/incorrect virto.cfg. Fixing
    this typo fixes the build for boards still using the 3.0 kernel.
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.4: uprobes: reinstate config options for 'uprobe' feature

bumping the meta SRCREV to import the following fix:

[
    uprobes: reinstate config options for 'uprobe' feature

    commit 17ec51adfff (meta: cleanup invalid/obselete 3.4 CONFIG options)
    removed the uprobes config options, this restores them.
]

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kernel-yocto: clarify KMETA branch comments

Having a meta branch is not strictly required by the tools (and
recipes like linux-yocto-custom do not have meta branches), but the
comments in the kernel-yocto.bbclass could lead someone to think that
it was required.

This commit clearifies the comment to the following:

  # We can fix up the kernel repository even if it wasn't a bare clone.
  # If KMETA is defined, the branch must exist, but a machine branch
  # can be missing since it may be created later by the tools.

[YOCTO #3422]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kern-tools: report missing config fragments by name

If a configuration fragment was missing, the previous error output
was not clear about the error:

  | [INFO] doing kernel configme
  | [INFO] Configuring target/machine combo: "standard/atom-pc"
  | [INFO] collecting configs in ./meta/meta-series
  | ERROR: could not sanitize configuration fragments
  |    errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log

but we know the name of the missing fragment and can improve the error
message to be this:

  | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found
  | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc
  | ERROR. Could not locate meta series for atom-pc
  | ERROR. Could not apply patches for atom-pc.
  |        Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)

[YOCTO #3473]

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