From: Raymond Danks <ray.danks@se-eng.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2 v2] mkelfimage: Add stable git build (initial recipe)
Date: Fri, 29 Jun 2012 14:03:41 -0600 [thread overview]
Message-ID: <4FEE0A1D.9070309@se-eng.com> (raw)
In-Reply-To: <4FEDEA1E.6080503@linux.intel.com>
On 06/29/2012 11:47 AM, Darren Hart wrote:
>
> On 06/29/2012 08:41 AM, Raymond Danks wrote:
>> Signed-off-by: Raymond Danks<ray.danks@se-eng.com>
>> ---
>> This was originally submitted to the openembedded project:
>> http://patches.openembedded.org/patch/7687/
>>
>> v2:
>> Remove depreciated NATIVE_INSTALL_WORKS
>>
>> meta/recipes-devtools/mkelfimage/mkelfimage_git.bb | 17 +++++++++++++++++
>> 1 files changed, 17 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/mkelfimage/mkelfimage_git.bb
>>
>> diff --git a/meta/recipes-devtools/mkelfimage/mkelfimage_git.bb b/meta/recipes-devtools/mkelfimage/mkelfimage_git.bb
>> new file mode 100644
>> index 0000000..1224a63
>> --- /dev/null
>> +++ b/meta/recipes-devtools/mkelfimage/mkelfimage_git.bb
>> @@ -0,0 +1,17 @@
>> +DESCRIPTION = "A utility to create ELF boot images from Linux kernel images"
>> +HOMEPAGE = "http://www.coreboot.org/Mkelfimage"
>> +SECTION = "devel"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM = "file://COPYING;md5=ea5bed2f60d357618ca161ad539f7c0a"
>> +
>> +SRCREV = "e13632a939e7dde8d7d44fc73e73a41dae8060c3"
>> +PV = "1.0.0+gitr${SRCPV}"
>> +PR = "r1"
> Minor, but I believe this should be "r0" for the initial creation of a
> recipe.
>
>
Yeah. That's debatable. I did send this to openembedded at one point.
Yes, this is the first time this is included in openembedded-core, but
it is different in that the patches that were applied in the previous
version are already upstreamed to coreboot in this version.
next prev parent reply other threads:[~2012-06-29 20:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 20:22 [PATCH 1/2] image_types: Add elf image type Raymond Danks
2012-06-22 20:22 ` [PATCH 2/2] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-06-29 12:19 ` Richard Purdie
2012-06-29 15:32 ` Raymond Danks
2012-06-29 15:41 ` [PATCH 1/2 v2] image_types: Add elf image type Raymond Danks
2012-06-29 17:45 ` Darren Hart
2012-06-29 20:01 ` Raymond Danks
2012-06-29 15:41 ` [PATCH 2/2 v2] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-06-29 17:47 ` Darren Hart
2012-06-29 20:03 ` Raymond Danks [this message]
2012-06-29 20:19 ` [PATCH 1/2 v3] image_types: Add elf image type Raymond Danks
2012-06-30 13:38 ` Darren Hart
2012-07-02 4:22 ` Saul Wold
2012-07-02 15:05 ` Raymond Danks
2012-07-02 16:51 ` Saul Wold
2012-07-02 19:00 ` Raymond Danks
2012-07-02 20:51 ` [PATCH 1/2 v4] " Raymond Danks
2012-07-05 17:35 ` Saul Wold
2012-06-29 20:30 ` [PATCH 2/2 v3] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-07-08 21:34 ` [PATCH 2/2] " Saul Wold
2012-07-09 19:20 ` Raymond Danks
2012-06-25 16:58 ` [PATCH 1/2] image_types: Add elf image type Darren Hart
2012-06-27 20:34 ` Raymond Danks
2012-06-27 20:43 ` Raymond Danks
2012-06-27 21:32 ` Darren Hart
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=4FEE0A1D.9070309@se-eng.com \
--to=ray.danks@se-eng.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox