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-24 07:19:17 +0100
commit03abfcb0341c93736b782781c1c2562c4c5e5e4b (patch)
treebfa190a7e1a1e44245bab15f8745e2abeab2a287
parent203eadfc04eca37b5e21c073e99ec19732ef6e9b (diff)
downloadpoky-03abfcb0341c93736b782781c1c2562c4c5e5e4b.tar.gz
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] (From OE-Core rev: d6a0c0f60ea85235479d968f75d067a10ce21574) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-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() {
163 patchme ${KMACHINE} 163 patchme ${KMACHINE}
164 if [ $? -ne 0 ]; then 164 if [ $? -ne 0 ]; then
165 bberror "Could not apply patches for ${KMACHINE}." 165 bberror "Could not apply patches for ${KMACHINE}."
166 bbfatal "Patch failures can be resolved in the devshell (bitbake -c devshell ${PN})" 166 bbfatal "Patch failures can be resolved in the linux source directory ${S})"
167 fi 167 fi
168 168
169 # check to see if the specified SRCREV is reachable from the final branch. 169 # check to see if the specified SRCREV is reachable from the final branch.