From: git@arago-project.org (Arago Project git)
To: meta-ti@yoctoproject.org
Subject: Cliff Brake : linux_3.1: add extra '#' to multi-line comment
Date: Fri, 25 Jan 2013 08:04:46 +0000 (UTC) [thread overview]
Message-ID: <20130125080446.4121452ADE@arago-project.org> (raw)
Module: meta-ti
Branch: master
Commit: 9273b57d956aa4cbbb97b27fd8f8d2581ce247da
URL: http://arago-project.org/git/meta-ti.git?a=commit;h=9273b57d956aa4cbbb97b27fd8f8d2581ce247da
Author: Cliff Brake <cbrake@bec-systems.com>
Date: Tue Jan 22 12:13:20 2013 -0500
linux_3.1: add extra '#' to multi-line comment
Bitbake is getting more particular:
ERROR: There is a confusing multiline, partially commented expression on
line 27 of file /scratch/oe/oe-build-core-3/sources/meta-ti/...
Please clarify whether this is all a comment or should be parsed.
Signed-off-by: Cliff Brake <cbrake@bec-systems.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
---
recipes-kernel/linux/linux_3.1.bb | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/recipes-kernel/linux/linux_3.1.bb b/recipes-kernel/linux/linux_3.1.bb
index 0ec0d26..d6ed98c 100644
--- a/recipes-kernel/linux/linux_3.1.bb
+++ b/recipes-kernel/linux/linux_3.1.bb
@@ -24,6 +24,7 @@ SRC_URI += "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;pro
# Needs refresh:
# file://beagle/0003-OMAP3-beagle-HACK-add-in-1GHz-OPP.patch \
+#
SRC_URI_append_beagleboard = " file://logo_linux_clut224.ppm \
next reply other threads:[~2013-01-25 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 8:04 Arago Project git [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-28 23:49 Cliff Brake : linux_3.1: add extra '#' to multi-line comment Arago Project git
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130125080446.4121452ADE@arago-project.org \
--to=git@arago-project.org \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.