From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] linux-libc-headers: provide 3.0.x and 3.1 headers
Date: Wed, 26 Oct 2011 16:26:49 -0400 [thread overview]
Message-ID: <4EA86D09.6070704@windriver.com> (raw)
In-Reply-To: <1319660702.9583.0.camel@ted>
On 11-10-26 04:25 PM, Richard Purdie wrote:
> On Wed, 2011-10-26 at 14:25 -0400, Bruce Ashfield wrote:
>> This changes makes two different 3.x headers available to the
>> toolchain. The latest 3.0.x and 3.1 tarballs. Compatibility is
>> maintained with older 2.6 headers by creating a new variable
>> that changes the SRC_URI based on the major version number of
>> the kernel.
>>
>> Tested with 2.6.37.2, 3.0.8 and 3.1 builds and boots.
>>
>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
>> ---
>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>> .../linux-libc-headers/linux-libc-headers.inc | 15 +++++-
>> .../linux-libc-headers/linux-libc-headers_3.0.8.bb | 53 ++++++++++++++++++++
>> .../linux-libc-headers/linux-libc-headers_3.1.bb | 53 ++++++++++++++++++++
>> 4 files changed, 120 insertions(+), 3 deletions(-)
>> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.0.8.bb
>> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.1.bb
>
> Can someone please explain to me why we don't move some of the bits in
> the .bb file into the .inc rather than duplicating it each time?
I wondered the same thing. I can refactor it if no one
objects.
Bruce
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2011-10-26 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 18:25 [PATCH 0/1] RFC: provide 3.0.x and 3.1 libc headers Bruce Ashfield
2011-10-26 18:25 ` [PATCH 1/1] linux-libc-headers: provide 3.0.x and 3.1 headers Bruce Ashfield
2011-10-26 20:25 ` Richard Purdie
2011-10-26 20:26 ` Bruce Ashfield [this message]
2011-10-26 21:01 ` Richard Purdie
2011-10-26 21:14 ` Anders Darander
2011-10-26 21:18 ` Anders Darander
2011-10-27 0:53 ` Bruce Ashfield
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=4EA86D09.6070704@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
/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