From: Carlos Hernandez <ceh@ti.com>
To: <meta-arago@arago-project.org>
Subject: [PATCH] AUTOREV recipe for linux-omap3-upstream-staging
Date: Wed, 5 Dec 2012 16:50:39 -0500 [thread overview]
Message-ID: <50BFC1AF.5060206@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 49 bytes --]
Please consider for meta-arago. Thanks,
Carlos
[-- Attachment #2: 0008-AUTOREV-recipe-for-linux-omap3-upstream-staging.patch --]
[-- Type: text/x-patch, Size: 1449 bytes --]
From 891b29b0ec22d81149e400d802fb56c4d7a6d6b1 Mon Sep 17 00:00:00 2001
From: Carlos Hernandez <ceh@ti.com>
Date: Tue, 4 Dec 2012 17:43:42 -0500
Subject: [PATCH 08/12] AUTOREV recipe for linux-omap3-upstream-staging
Signed-off-by: Carlos Hernandez <ceh@ti.com>
---
.../linux/linux-omap3-upstream-staging_git.bb | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 meta-arago-distro/recipes-kernel/linux/linux-omap3-upstream-staging_git.bb
diff --git a/meta-arago-distro/recipes-kernel/linux/linux-omap3-upstream-staging_git.bb b/meta-arago-distro/recipes-kernel/linux/linux-omap3-upstream-staging_git.bb
new file mode 100644
index 0000000..871b6a8
--- /dev/null
+++ b/meta-arago-distro/recipes-kernel/linux/linux-omap3-upstream-staging_git.bb
@@ -0,0 +1,20 @@
+require linux-omap3.inc
+
+DESCRIPTION = "Linux kernel for Omap3 from Upstream staging tree"
+
+BRANCH = "refs/heads/master"
+
+COMPATIBLE_MACHINE = "am37x-evm|am3517-evm|dm37x-evm|am3517-evm|am387x-evm|am389x-evm|am335x-evm|beagleboard"
+
+PV = "3.7"
+KVER = "${PV}"
+SRCREV = "${AUTOREV}"
+
+MACHINE_KERNEL_PR_append = "+gitr${SRCPV}"
+
+SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git;protocol=git;branch=${BRANCH}"
+
+SRC_URI_append_beagleboard = " file://beagleboard/defconfig \
+"
+SRC_URI_append_am335x-evm = " file://am335x-evm/defconfig \
+"
--
1.7.0.4
reply other threads:[~2012-12-05 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50BFC1AF.5060206@ti.com \
--to=ceh@ti.com \
--cc=meta-arago@arago-project.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.