{"push_id":906604989,"size":26,"distinct_size":0,"ref":"refs/heads/fido","head":"9dd410e8e301c74c73d5fa6173ff6d62b5dabf05","before":"115e5ccff5ede7e2b7a2c4439e137240263086f0","commits":[{"sha":"d855db99dc1c62828239dcb20972024adb050ea3","author":{"email":"2cb6ee6ce0e123005c8f8e74b183542259331faf@intel.com","name":"Gayatri Kammela"},"message":"luv-test-manager: Relocate warning messages' strings\n\nLUV alerts about different issues by displaying warning messages on the\nsplash screen (blue screen) when a given situations occurs.\n\nRelocate the warnings strings to a designated section at the top of the\nfile and assing descriptive names. This improves readability and grouping\nthem together improves maintainability.\n\nCc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>\nSigned-off-by: Gayatri Kammela <gayatri.kammela@intel.com>\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/d855db99dc1c62828239dcb20972024adb050ea3"},{"sha":"f572bb4399ea7b1f576e531774d0b5d69bc2790e","author":{"email":"2cb6ee6ce0e123005c8f8e74b183542259331faf@intel.com","name":"Gayatri Kammela"},"message":"luv-test-manager: Add a warning message when removable disk is full\n\nLUV supports multiple runs and saves results back onto the removable disk.\nAt some point the disk could be full and LUV will not be able to save the\nresults.\n\nModify luv-test-manager to add a threshold level of 2MB and warn user when the\ndisk space is below such threshold limit by displaying \"Removable disk space is\nrunning low , please backup and empty the disk to try again !!\" on the splash\nscreen.\n\nAlso, correct the luv-storage mount point string to be able to get detected the\nleft space through df command.\n\nCc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>\nSigned-off-by: Gayatri Kammela <gayatri.kammela@intel.com>\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/f572bb4399ea7b1f576e531774d0b5d69bc2790e"},{"sha":"28118edbff509067591bcb81906748616c56fd2c","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits-python: _ctypes: do not use the WIN/64/EFI64 calling convention\n\nThe commit ID f6b5a91f417ac77d2fe9b0b3eb66293db132e2e in BITS implemented\nsupport for the WIN64/EFI64. However, this was only implemented in the libffi\nmodule that GRUB uses, not on the host Python implementation. Thus,\nPython fails to build with the following error:\n\n../build/python-host/Modules/_ctypes/callbacks.c:465:14: In function '_ctypes_alloc_callback':\nerror: 'FFI_EFI64' undeclared (first use in this function)\n         cc = FFI_EFI64;\n              ^\nHence, for now just do not use such calling convention in the host Python. This\neffectively reverts commit 2e41220a584b0d4fcda5c95dc14cf638f9b9a331 in\nthe Python submodule of BITS.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/28118edbff509067591bcb81906748616c56fd2c"},{"sha":"0a7dca74abfb07996e6720d8550265d60224d3f4","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits-python: python: configure: customize Python version\n\nBITS is built with a specific version of Python that is shipped along with BITS.\nWe could try to build with the nativesdk Python but we might run unto build\nor runtime problems. Hence, it is better to use the BITS Python. I order for the\nnativesdk and BITS' Python to coexist, modify the version in BITS Python.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/0a7dca74abfb07996e6720d8550265d60224d3f4"},{"sha":"c04672d6578cb9ff097c539576600dd21b7adfa6","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits-python: customize the Python install bin directory\n\nCustomize the Python bin directory to allow it to be installed within\nthe LUV native sysroot. Please note that the bin directory is set as BINDIR/PN.\nThis text is intended to be replaced at build time by bitbake with\nthe appropriate value.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/c04672d6578cb9ff097c539576600dd21b7adfa6"},{"sha":"5befdad2a462e09e571c3992bf82ffed50bfd7bf","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"recipes-devtools: add BITS Python recipe\n\nThe BIOS Implementation Test Suite (BITS) is a test suite that runs embedded in\na GRUB bootloader. Given that BITS tests are run using Python, A modified\nversion of Python is ported into GRUB. Furthermore, The Python versions that\nBITS used is maintained as a git submodule in the BITS repository.\n\nBITS Python needs to be installed as part of the nativesdk to be used when\nbuilding the BITS Python modules.\n\nGiven that bitbake already has a version of Python as part of the nativesdk,\nthis recipe modifies slightly both the version and the install directory of\nBITS Python. When the build is complete. BITS can invoke its Python using\nbitspython.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/5befdad2a462e09e571c3992bf82ffed50bfd7bf"},{"sha":"84ceac4885683137927070931365cd5462ea765d","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: grub: core: lib: crypto: complete handling fgets return  values\n\nHandle return values of fgets when reading the password string. While we can\nobtain the length of the captured string by using strlen (buf), we still get\nbuild warnings if the return values of fgets are not handled. Also, it is more\nclear to handle the fgets value separately. This is the warning issued by the\ncompiler:\n\n    build/grub/grub-core/lib/crypto.c: In function 'grub_password_get':\n    build/grub/grub-core/lib/crypto.c:431:9: error: ignoring return value of 'fgets',\n       declared with attribute warn_unused_result [-Werror=unused-result]\n           fgets (buf, buf_size, stdin);\n                 ^\n\nfgets returns the number of characters read, or NULL when an error occurred or\nno characters were read. Thus, we can return 0 in such a case. Furthermore,\nthe callers of this function check on zero values for errors.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/84ceac4885683137927070931365cd5462ea765d"},{"sha":"5fa297539cafa59da9175d6b64575bde55889e58","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: grub:: util: of: complete handling of read return values\n\nReturn values of read are not checked for errors. This can lead to spurious\nreads. Furthermore, it triggers the following compiler warning:\n\n    build/grub/util/ieee1275/ofpath.c: In function 'find_obppath':\n    build/grub/util/ieee1275/ofpath.c:146:11: error: ignoring return value of\n        'read', declared with attribute warn_unused_result [-Werror=unused-result]\n           read(fd, of_path, size);\n               ^\n    build/grub/util/ieee1275/ofpath.c: In function 'check_sas':\n    build/grub/util/ieee1275/ofpath.c:357:8: error: ignoring return value of\n        'read', declared with attribute warn_unused_result [-Werror=unused-result]\n       read (fd, phy, sizeof (phy));\n            ^\nIt makes sense to return NULL when reads fail, as the callers of this\nfunction of find_obppath checks for NULL values when handing errors.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/5fa297539cafa59da9175d6b64575bde55889e58"},{"sha":"3170789fcb10b5ed18c17eb3146920baab043314","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: grub: core: net: bootp: conserve variable qualifier\n\nThe function set_env_limn_ro receives *vend as pointer to a constant. However\nthe automatic variables *ptr and *ptr0 drop such qualifier, causing this\nwarning:\n\n    build/grub/grub-core/net/bootp.c: In function 'grub_net_configure_by_dhcp_ack':\n    build/grub/grub-core/net/bootp.c:255:30: error: passing argument 2 of\n      'parse_dhcp_vendor' discards 'const' qualifier from pointer target type\n       [-Werror=discarded-array-qualifiers]\n          parse_dhcp_vendor (name, &bp->vendor, size - OFFSET_OF (vendor, bp), &mask);\n                                  ^\n    build/grub/grub-core/net/bootp.c:55:1: note: expected 'void *' but argument is\n      of type 'const grub_uint8_t (*)[] {aka const unsigned char (*)[]}'\n           parse_dhcp_vendor (const char *name, void *vend, int limit, int *mask)\n           ^\n\nThese variables do not change the contents of *vend. Thus, we simply add\nthe const qualifier.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/3170789fcb10b5ed18c17eb3146920baab043314"},{"sha":"515d7d9c1746b4c272cb20cb2daeefd9c05931a1","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: rc: python: use fwrap to build python\n\nIf this flag is not used, the following compiler warning is observed:\n\n    grub/grub-core/contrib-deps/python/Modules/arraymodule.c:1794:19:\n    error: assuming signed overflow does not occur when assuming that\n    (X + c) < X is always false [-Werror=strict-overflow]\n          if ((step > 0 && stop < start) ||\n                        ^\n\nFurthermore, stand-alone builds of Python are built using the -fwrap cflag to\ninstruct the compiler to not optimize comparions between signed\nvariables that can wrap. Thus, we simply add the flag.\n\nAlso, by analizing the function in question (array_ass_subscr), one can\nobserve there exists at least one code path that leads to the (X + c) < X\ncomparison. This could occur if the value argument is NULL. In such a case,\nstep = 1, start = i, stop = + 1; which leads to:\n\n    step > 0 && stop  < start\n    1    > 0 && i + 1 < i\n\nThe second portion of the comparison is always false, provided that\ni does not wrap around.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/515d7d9c1746b4c272cb20cb2daeefd9c05931a1"},{"sha":"11d8d45b0dedd3e27a136f6f36674edfc5fae83b","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: grub: adjust configure params for bitbake\n\nGRUB is built both natively and for target. In order to accommodate builds\nvia bitbake sysroot, the --target --build and --host parameters passed to\nconfigure need to be adjusted at build time for either native or target builds.\nUnder bitbake, this is usually done by the autotools recipe via the do_configure\ntask. However, the construction of the BITS makefile makes it difficult to use\nthe autotools recipe. Thus, we make the adjustment manually.\n\nPlease note that the parameters --target, --build and --host are set as\nTARGET_SYS, BUILD_SYS and HOST_SYS. These names are adjusted by the BITS\nbitbake recipe using stream edition at build time.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/11d8d45b0dedd3e27a136f6f36674edfc5fae83b"},{"sha":"7b5c30bfecaf1cd06f1efa98b925f16394883113","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: split grub build from image generation\n\nGenerate the grub image using a separate make target. This eases the creation\nof grub images when BITS is built within automated build infrastructures, such\nas bitbake.\n\nAlso, as part of the build process of BITS for a target, a native build of BITS\nwill be created. This will create a native grub-mkimage that can be used to\ngenerate grub images when building for a particular target. Such native\ngrub-mkimage can be invoked with bits-grub-mkimage. This avoid conflicts with\nthe existing grub-mkimage provided by the grub-efi recipe.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/7b5c30bfecaf1cd06f1efa98b925f16394883113"},{"sha":"c75a532e88b2d485c384e64b952c5da020fbcb10","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: do not depend bytecompile-% on build-python-host\n\nAs part of the build process of BITS within bitbake, the Python version\nthat BITS needs is built separately and is available at the time BITS is built\nfor a target. Thus, we can drop this dependency. The dependency will be spelled\nout on the bitbake recipe used to build BITS for a target as:\n\n DEPENDS = \"... bits-python-native\"\n\nAlso, such BITS-specific version of Python is available by invoking bitspython.\nThe definition of bytecompile is updated accordingly to reflect this fact.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/c75a532e88b2d485c384e64b952c5da020fbcb10"},{"sha":"a09b1a417b5dc24380d3a5ae27ac65aea50c94a2","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: allow incremental builds\n\nBITS makefile utilizes target names not as filenames but as task names. For\ninstance, setup does not actually create a target file named setup. Furthermore,\nfor a given target (a task, actually) the dependencies are other tasks, not\nfiles. Thus, make will not find such files and and therefore determine that all\nthe targets need to be rebuilt every time, even when present. This is form of\nutilizing make is problematic when, for instance, we want build BITS in separate\nstages (e.g., build GRUB components and create the GRUB image separately).\n\nFurthermore, at each invocation of make, the makefile instructs to delete all\nthe build directories.\n\nIn order to allow incremental builds, a fake target file is created along with\neach individual target (a task, actually) . Thus, in subsequent builds, a task\nwill only be executed if the fake target file is missing. This fake target\nfile simply echoes to the target file the name of the task executed.\n\nThis mechanism can only work if we don't remove the build directories when\nmake is called. Such deletion is removed from the setup task. They will be\ndeleted in the clean target.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/a09b1a417b5dc24380d3a5ae27ac65aea50c94a2"},{"sha":"e92b91250599a86152bafa7c370962cfc3462092","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: bits-cfg.txt: Set batch mode\n\nLUV runs BITS in batch mode. Thus, enable it.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/e92b91250599a86152bafa7c370962cfc3462092"},{"sha":"df850c82c90628c38451f4ce53174a305bd476c4","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: init.cfg: Exit BITS upon completion\n\nBITS is implemented on top of GRUB. LUV has its own bootloader. Thus, in\norder to run BITS. LUV chainloads the BITS GRUB. Hence, when BITS completes\nexecution, LUV needs it to exit and return to the LUV bootloader to continue\nwith other tests.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/df850c82c90628c38451f4ce53174a305bd476c4"},{"sha":"dceb28df9866f96acc4d0fb08e33040d94ce8b6e","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"bits: refactor recipe to allow BITS builds\n\nRecently the BIOS Implementation Test Suite has published a git repository with\nits source code. This makes it easier to build BITS in the LUV layer and the\nrecipe is refactored for this purpose. The ability to build BITS comes handy if\nwe want/need to implement tweaks in the code (e.g., run BITS from a ramdisk\nrather than a physical disk).\n\nThis recipe adds support both target and native builds. The native target is\nintended to provide a grub-mkimage that can be used by bitbake to generate the\nGRUB bootable image. Currently supported targets are x86 and x86_64.\n\nBITS implements large portions of its code in Python and needs its own Python\nversion. Such implementation is built separately using the bits-python-recipe.\n\nThis recipe uses several patches to tweak the BITS behavior to suit LUV. For\ninstance, BITS has a master makefile that erases and rebuilds everything at each\nbuild. Also, BITS makefile treats target names as tasks. In order to adapt BITS\nto the bitbake build paradigm, it needs to support incremental builds. Also,\nseveral build warnings are fixed.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/dceb28df9866f96acc4d0fb08e33040d94ce8b6e"},{"sha":"ddf31d76144232e4d9c7fbdf605a41c2eafb3b02","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"chipsec: setup.py: install files via package_data\n\nThiebaud Weksteen submitted a pull request to chipsec\n(https://github.com/chipsec/chipsec/pull/11) to use package_data instead of\ndata_files in the chipsec setup script to determine correctly the installation\npath of the chipsec XML configuration files. This is an except of the Thiebaud's\ndescripton:\n\n\"Unfortunately, it is not possible to guess the exact directory where the\npackage will be installed. Using virtualenv on Ubuntu, the target directory is\n\"lib/python2.7/site-packages/chipsec/cfg\" and not\n'Lib/site-packages/chipsec/cfg'.\" (https://github.com/chipsec/chipsec/issues/12)\n\nThis pull request has been taken in LUV while the discussion continues in\nthe chipsec mailing list (chipsec@lists.01.org).\n\nAlso, given that now package_data is used instead of data_files, we can drop\nthe patch 0005-tool-setup.py-Delete-Windows-drivers-from-data_files.patch which\nskipped the installation of Windows-specific files in Linux via data_files.\n\nReported-by: Darren Bilby <darrenbilby@gmail.com>\nCc: Thiebaud Weksteen <tweek@google.com>\nCc: Blibbet <blibbet@gmail.com>>\nCc: John Loucaides <john.loucaides@intel.com>\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/ddf31d76144232e4d9c7fbdf605a41c2eafb3b02"},{"sha":"428f77acab43c473c89b7293782812b00a397043","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"core-image-efi-initramfs: add python modules needed by chipsec\n\nFor parsing the XML configuration files, chipsec needs the python-codecs module.\nOtherwise, this error is observed:\n\n    [*] looking for platform config in '/usr/lib/python2.7/site-packages/chipsec\n        /cfg/common.xml'..\n    [-] Traceback (most recent call last):\n      File \"/usr/lib/python2.7/site-packages/chipsec/chipset.py\", line 418, in\n        init_cfg self.init_xml_configuration()\n      File \"/usr/lib/python2.7/site-packages/chipsec/chipset.py\", line 323, in\n        init_xml_configuration self.init_cfg_xml\n        ( os.path.join(_cfg_path,'common.xml'), self.code )\n      File \"/usr/lib/python2.7/site-packages/chipsec/chipset.py\", line 339, in\n        init_cfg_xml tree = ET.parse( fxml )\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 1182, in parse\n        tree.parse(source, parser)\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 656, in parse\n        parser.feed(data)\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 1640, in feed\n        self._parser.Parse(data, 0)\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 1538, in\n        _start_list tag = fixname(tag)\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 1523, in _fixname\n        self._names[key] = name = self._fixtext(name)\n      File \"/usr/lib/python2.7/xml/etree/ElementTree.py\", line 1511, in _fixtext\n        return text.encode(\"ascii\")\n    LookupError: no codec search functions registered: can't find encoding\n\nThe subprocess modules is neede by the chipsec SMMR module. If missing, this\nerror is observed:\n\n    [*] Verifying that SMRR range base & mask are the same on all logical CPUs..\n    [-] Traceback (most recent call last):\n      File \"/usr/lib/python2.7/site-packages/chipsec_main.py\", line 291, in\n        run_module result = modx.run( module_argv )\n      File \"/usr/lib/python2.7/site-packages/chipsec/module.py\", line 80, in run\n        result = self.mod_obj.run(module_argv)\n      File \"/usr/lib/python2.7/site-packages/chipsec/modules/common/smrr.py\",\n        line 165, in run return self.check_SMRR( do_modify )\n      File \"/usr/lib/python2.7/site-packages/chipsec/modules/common/smrr.py\",\n        line 115, in check_SMRR for tid in\n        range(self.cs.msr.get_cpu_thread_count()):\n      File \"/usr/lib/python2.7/site-packages/chipsec/hal/msr.py\", line 70, in\n        get_cpu_thread_count thread_count = self.helper.get_threads_count()\n      File \"/usr/lib/python2.7/site-packages/chipsec/helper/oshelper.py\",\n        line 327, in get_threads_count return self.helper.get_threads_count()\n      File \"/usr/lib/python2.7/site-packages/chipsec/helper/linux/helper.py\",\n        line 761, in get_threads_count import subprocess\n    ImportError: No module named subprocess\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/428f77acab43c473c89b7293782812b00a397043"},{"sha":"d30a12175ff3c28c4af1fb1a76d61544cf1a42b6","author":{"email":"b0ea9152ea2026377af95cd4fdb162e220f5b6e2@linux.intel.com","name":"Ricardo Neri"},"message":"chipsec: setup.py: install cores library under helper/linux\n\nSimply setting 'cores' in the constructor of Extension causes the library\nto be installed under the root of the package. However, the helper.py module\nexpects to find it under [package-root]/helper/linux. Thus, install the library\nwhere helper.py can find it.\n\nAlso, add the new location to the list of debug files.\n\nSigned-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/01org/luv-yocto/commits/d30a12175ff3c28c4af1fb1a76d61544cf1a42b6"}]}