summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2015-05-12 16:21:45 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-05-22 13:34:30 +0100
commitd6a0c0f60ea85235479d968f75d067a10ce21574 (patch)
tree230810f94028f3f69e261a344b55f0803a9d7298
parent121498714b03339d2e5090c2a8fe0618bbaa8610 (diff)
downloadopenembedded-core-contrib-d6a0c0f60ea85235479d968f75d067a10ce21574.tar.gz
openembedded-core-contrib-d6a0c0f60ea85235479d968f75d067a10ce21574.tar.bz2
openembedded-core-contrib-d6a0c0f60ea85235479d968f75d067a10ce21574.zip
linux-yocto: drop suggestion of devshell for patch failures
When a patch fails to apply, the kernel-yocto bbclass attempted to be helpful and suggest that devshell be used to fix the issue. The only problem is that you can't get to devshell if a patch is failing. We drop this bad advise and instead point to the linux source directory. [YOCTO: #6202] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-rw-r--r--meta/classes/kernel-yocto.bbclass2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 88588d7cac..6fd025ef1e 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -163,7 +163,7 @@ do_patch() {
patchme ${KMACHINE}
if [ $? -ne 0 ]; then
bberror "Could not apply patches for ${KMACHINE}."
- bbfatal "Patch failures can be resolved in the devshell (bitbake -c devshell ${PN})"
+ bbfatal "Patch failures can be resolved in the linux source directory ${S})"
fi
# check to see if the specified SRCREV is reachable from the final branch.