* Matthew Garrett <matthew.garr...@coreos.com> wrote:
> Any feedback on this?
So I worry about:
- the fragmented nature of it: lots of non-obvious pieces of code
will now be scattered all around arch/x86/.
- the crazy #ifdefs scattered around
- the various pieces of data scattered around
... so while I don't mind the feature in principle, but it should be
centralized much better IMHO, made Kconfig invariant at least in its
fragmented callbacks, with only the very strictly boot method specific
details spelled out explicitly.
I have not thought much about how to achieve that :-/
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
