[U-Boot] [PATCH] buildman: Fix building based on 'options' field

The README for buildman says that we can use any field in boards.cfg to decide what to build. However, we were not saving the options field correctly.
Cc: Simon Glass sjg@chromium.org Signed-off-by: Tom Rini trini@konsulko.com --- tools/buildman/board.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/buildman/board.py b/tools/buildman/board.py index 5d536d5f2004..ae0e0b8e1719 100644 --- a/tools/buildman/board.py +++ b/tools/buildman/board.py @@ -92,9 +92,9 @@ class Board: self.board_name = board_name self.vendor = vendor self.soc = soc - self.props = [self.target, self.arch, self.cpu, self.board_name, - self.vendor, self.soc] self.options = options + self.props = [self.target, self.arch, self.cpu, self.board_name, + self.vendor, self.soc, self.options] self.build_it = False

On 4 November 2016 at 20:59, Tom Rini trini@konsulko.com wrote:
The README for buildman says that we can use any field in boards.cfg to decide what to build. However, we were not saving the options field correctly.
Cc: Simon Glass sjg@chromium.org Signed-off-by: Tom Rini trini@konsulko.com
tools/buildman/board.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Acked-by: Simon Glass sjg@chromium.org

On Fri, Nov 04, 2016 at 10:59:45PM -0400, Tom Rini wrote:
The README for buildman says that we can use any field in boards.cfg to decide what to build. However, we were not saving the options field correctly.
Cc: Simon Glass sjg@chromium.org Signed-off-by: Tom Rini trini@konsulko.com Acked-by: Simon Glass sjg@chromium.org
Applied to u-boot/master, thanks!
participants (2)
-
Simon Glass
-
Tom Rini