syz-kconf: execute shell snippets in reverse loading order

Background:
- syz-kconf loads and overlays config fragments to form a final kernel
  config. Fragments are loaded top to bottom as defined in the includes
  section of main.yml or your downstream syz-kconf config.
- A config fragment loaded later can override kconf options set by an
  earlier loaded fragment. However the override keyword can only be used
  if an earlier fragment really did set the same option. Otherweise an
  error is raised.
- With this in mind it makes sense to load fragments from broadest scope
  to most specific e.g. base -> x86_64 -> chromeos, so that chromeos can
  override a setting usually enabled on x86_64 machines.

The Problem:
- Before this change shell snippets were executed in order they were
  loaded from the fragments.
- This is unfortunate as the broad fragments like x86_64.yml expect to
  operate on an existing .config with their shell snippets. Meanwhile
  some downstream distros like icebreaker generate their config using
  such a shell snippet.
- Hence ordering the fragments like base -> x86_64 -> icebreaker results
  in an error about the x86_64 not finding a .config without this
  change. Meanwhile ordering icebreaker -> base -> x86_64 works, but
  means the icebreaker fragment can't override x86_64 kconf options.

The Solution:
- This change resolves the problem outlined above by reversing the order
  shell snippets are executed. Now shell snippets will be executed
  starting with the most recently loaded fragment. This way the proposed
  fragment order base -> x86_64 -> icebreaker becomes viable.
- Luckily the shell section isn't heavily used, so this change didn't
  result in meaningfull final config changes.

0 files changed, 0 insertions, 0 deletions