From: Denys Dmytriyenko <denys@ti.com>
To: "Franklin S. Cooper Jr" <fcooper@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33
Date: Mon, 19 Aug 2013 17:36:13 -0400 [thread overview]
Message-ID: <20130819213613.GF32524@denix.org> (raw)
In-Reply-To: <1375317112-1690-1-git-send-email-fcooper@ti.com>
On Wed, Jul 31, 2013 at 07:31:46PM -0500, Franklin S. Cooper Jr wrote:
> * This is the version that was originally being using in arago/oe-classic based
> SDK.
Why do we need 2.6.33? All our old kernels are at least 2.6.37 now and there
is corresponding linux-libc-headers available...
> Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
> ---
> .../linux-libc-headers_2.6.33.bb | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
> create mode 100644 meta-arago-extras/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.33.bb
>
> diff --git a/meta-arago-extras/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.33.bb b/meta-arago-extras/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.33.bb
> new file mode 100644
> index 0000000..eb8cb19
> --- /dev/null
> +++ b/meta-arago-extras/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.33.bb
> @@ -0,0 +1,10 @@
> +require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
> +
> +FILESEXTRAPATHS_append := "${THISDIR}/${PN}:${COREBASE}/meta/recipes-kernel/linux-libc-headers/${PN}"
> +
> +PR = "r0"
> +
> +SRC_URI += " file://connector-msg-size-fix.patch"
> +SRC_URI[md5sum] = "c3883760b18d50e8d78819c54d579b00"
> +SRC_URI[sha256sum] = "63e237de3b3c4c46a21833b9ce7e20574548d52dabbd1a8bf376041e4455d5c6"
> +
> --
> 1.7.0.4
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>
next prev parent reply other threads:[~2013-08-19 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 0:31 [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33 Franklin S. Cooper Jr
2013-08-01 0:31 ` [master & danny][PATCH 2/7] arago.conf: Set machines to use " Franklin S. Cooper Jr
2013-08-01 0:31 ` [master & danny][PATCH 3/7] branding-amsdk: Set linux-libc-headers to 3.2 Franklin S. Cooper Jr
2013-08-19 21:37 ` Denys Dmytriyenko
2013-08-01 0:31 ` [master & danny][PATCH 4/7] arago-perfs.inc: Set linux-libc-header version to 3.2 for beagleboard Franklin S. Cooper Jr
2013-08-01 0:31 ` [master & danny][PATCH 5/7] arago.conf: Separate work directories by linux-libc-headers version Franklin S. Cooper Jr
2013-08-01 0:31 ` [master & danny][PATCH 6/7] toolchain-external-linaro: Use separate linux-libc-headers provider Franklin S. Cooper Jr
2013-08-19 21:41 ` Denys Dmytriyenko
2013-08-01 0:31 ` [master & danny][PATCH 7/7] meta-toolchain-arago: Add in linux-libc-headers version to variable Franklin S. Cooper Jr
2013-08-19 21:36 ` Denys Dmytriyenko [this message]
2013-08-20 2:30 ` [master & danny][PATCH 1/7] linux-libc-headers: Add linux-libc-headers version 2.6.33 Cooper Jr., Franklin
2013-08-20 16:23 ` Denys Dmytriyenko
2013-08-20 16:54 ` Cooper Jr., Franklin
2013-08-20 17:21 ` Denys Dmytriyenko
2013-08-20 17:38 ` Cooper Jr., Franklin
2013-08-20 17:44 ` Denys Dmytriyenko
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=20130819213613.GF32524@denix.org \
--to=denys@ti.com \
--cc=fcooper@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.