23e866da20
When libpayload header files are included in the payload itself, it's possible that the payloads config settings will conflict with the ones in libpayload. It's also possible for the libpayload config settings to conflict with the payloads. To avoid that, the libpayload config settings have _LP_ (for libpayload) added to them. The symbols themselves as defined in the Config.in files are still the same, but the prefix added to them is now CONFIG_LP_ instead of just CONFIG_. BUG=chrome-os-partner:19420 TEST=Built and booted on pit. Built libpayload and depthcharge on all supported platforms. BRANCH=None Change-Id: Ib8a46d202e7880afdeac7924d69a949bfbcc5f97 Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://gerrit.chromium.org/gerrit/65303 Reviewed-by: Stefan Reinauer <reinauer@google.com> Tested-by: Gabe Black <gabeblack@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org> |
||
|---|---|---|
| .. | ||
| config.bolt | ||
| config.daisy | ||
| config.falco | ||
| config.fox_baskingridge | ||
| config.fox_wtm2 | ||
| config.link | ||
| config.lumpy | ||
| config.peach_kirby | ||
| config.peach_pit | ||
| config.peppy | ||
| config.slippy | ||
| defconfig | ||