Skip to contentSkip to conversation

kernel-fitimage.bbclass: Create a "fitImage" symlink to resulting 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: Create a "fitImage" symlink to resulting FIT image.

From: Walter Goossens <[email protected]>

If an initramfs was used, the fitImage link will point to the FIT containing the initramfs. Otherwise it will link to the FIT without initramfs.

This ensures the user can depend on "fitImage" to point to the desired FIT image.

---
 meta/classes/kernel-fitimage.bbclass | 3 +++
 1 file changed, 3 insertions(+)
meta/classes/kernel-fitimage.bbclass +3 -0
index 6d02d74..b672579 100644
@@ -496,6 +496,9 @@ kernel_do_deploy_append() {
 		if [ -n "${INITRAMFS_IMAGE}" ]; then
 			ln -sf ${its_initramfs_base_name}.its ${its_initramfs_symlink_name}.its
 			ln -sf ${fit_initramfs_base_name}.bin ${fit_initramfs_symlink_name}.bin
+			ln -sf ${fit_initramfs_base_name}.bin fitImage
+		else
+			ln -sf ${linux_bin_base_name}.bin fitImage
 		fi
 	fi
 }
Signature · 1 line
2.7.4
#1 lore raw

✗ patchtest: failure for kernel-fitimage.bbclass: Create a "fitImage" symlink to resulting FIT image.

== Series Details ==

Series: kernel-fitimage.bbclass: Create a "fitImage" symlink to resulting FIT image.
Revision: 1
URL : https://patchwork.openembedded.org/series/13861/
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