From: Carlos Hernandez <ceh@ti.com>
To: <meta-arago@arago-project.org>
Subject: [PATCH] linux-stable recipe
Date: Wed, 5 Dec 2012 16:48:09 -0500 [thread overview]
Message-ID: <50BFC119.7050004@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
The nightly build script takes care of:
1) checking if there is a new tag
2) In case there is, set SRCREV to new tag and build.
Please consider for meta-arago. Thanks,
Carlos
[-- Attachment #2: 0007-linux-stable-recipe.patch --]
[-- Type: text/x-patch, Size: 1377 bytes --]
From e3d2c97ed7adbe9a7123484bc4ff36b86dd6f795 Mon Sep 17 00:00:00 2001
From: Carlos Hernandez <ceh@ti.com>
Date: Tue, 4 Dec 2012 17:42:41 -0500
Subject: [PATCH 07/12] linux-stable recipe
Signed-off-by: Carlos Hernandez <ceh@ti.com>
---
.../recipes-kernel/linux/linux-omap3-stable_git.bb | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 meta-arago-distro/recipes-kernel/linux/linux-omap3-stable_git.bb
diff --git a/meta-arago-distro/recipes-kernel/linux/linux-omap3-stable_git.bb b/meta-arago-distro/recipes-kernel/linux/linux-omap3-stable_git.bb
new file mode 100644
index 0000000..e59f334
--- /dev/null
+++ b/meta-arago-distro/recipes-kernel/linux/linux-omap3-stable_git.bb
@@ -0,0 +1,20 @@
+require linux-omap3.inc
+
+DESCRIPTION = "Linux kernel for Omap3 from mainline kernel.org"
+
+BRANCH = "refs/heads/master"
+
+COMPATIBLE_MACHINE = "am37x-evm|am3517-evm|dm37x-evm|am3517-evm|am387x-evm|am389x-evm|am335x-evm|beagleboard"
+
+SRCREV = "v3.2.9"
+PV = "3.6"
+KVER = "${PV}"
+
+MACHINE_KERNEL_PR_append = "+gitr${SRCPV}"
+
+SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.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:48 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=50BFC119.7050004@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.