Skip to contentSkip to conversation

kernel-fitimage.bbclass: Wrong binary was deployed for kernel-only FIT image.

PATCH In review Leon Woestenberg 2 participants 2 messages Sep 3, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 kernel-fitimage.bbclass: Wrong binary was deployed for kernel-only FIT image.

The kernel-fitimage.bbclass always outputs one FIT image without initramfs. This variant did deploy the kernel image itself rather than the FIT image.

(The FIT with initramfs was correctly deployed.)

---
 meta/classes/kernel-fitimage.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes/kernel-fitimage.bbclass +1 -1
index 50a91e1..16499c8 100644
@@ -463,7 +463,7 @@ kernel_do_deploy_append() {
 		install -m 0644 fit-image.its ${DEPLOYDIR}/${its_base_name}.its
 		linux_bin_base_name="fitImage-linux.bin-${PV}-${PR}-${MACHINE}-${DATETIME}"
 		linux_bin_symlink_name=fitImage-linux.bin-${MACHINE}
-		install -m 0644 linux.bin ${DEPLOYDIR}/${linux_bin_base_name}.bin
+		install -m 0644 arch/${ARCH}/boot/fitImage ${DEPLOYDIR}/${linux_bin_base_name}.bin
 
 		if [ -n "${INITRAMFS_IMAGE}" ]; then
 			echo "Copying fit-image-${INITRAMFS_IMAGE}.its source file..."
Signature · 1 line
2.7.4
#1 lore raw

✗ patchtest: failure for kernel-fitimage.bbclass: Wrong binary was deployed for kernel-only FIT image.

== Series Details ==

Series: kernel-fitimage.bbclass: Wrong binary was deployed for kernel-only FIT image.
Revision: 1
URL : https://patchwork.openembedded.org/series/13859/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 853e0499be)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe