From: Darren Hart <dvhart@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Poky <poky@yoctoproject.org>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] kernel: Add kernel-headers package for target module build
Date: Thu, 28 Jun 2012 23:14:47 -0700 [thread overview]
Message-ID: <4FED47D7.7080107@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sojfidUA9mne_RfXz+tE8d3pRboHbGxJL-dLD5wkeKVRw@mail.gmail.com>
On 06/28/2012 11:04 PM, Khem Raj wrote:
> On Thu, Jun 28, 2012 at 10:50 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>>
>> However, I don't have a strong opinion here, I'll happily call it
>> kernel-devel if that is strongly preferred by some.
>
> in oe terminology it will be -dev
THe other reason I didn't go that route is that we already have a
kernel-dev (although I don't much like the way it is used):
From kernel.bbclass:
PACKAGES = "kernel kernel-base kernel-vmlinux kernel-image kernel-dev \
kernel-misc kernel-headers"
FILES = ""
FILES_kernel-image = "/boot/${KERNEL_IMAGETYPE}*"
FILES_kernel-dev = "/boot/System.map* /boot/Module.symvers* /boot/config*"
FILES_kernel-vmlinux = "/boot/vmlinux*"
# misc is a package to contain files we need in staging
FILES_kernel-misc = "/kernel/include/config /kernel/scripts
/kernel/drivers/crypto /kernel/drivers/media"
FILES_kernel-headers = "/usr/src/kernel-headers"
And looking at that it appears I broke kernel-misc by moving things to
/usr/src (didn't notice that in my testing).
How would you propose we redefine the above in order to use "kernel-dev"
for the new package?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-29 6:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 4:17 [PATCH 0/4] Enable building modules on target Darren Hart
2012-06-29 4:17 ` [PATCH 1/4] linux-libc-headers-yocto: Do not include linux-yocto Darren Hart
2012-06-29 13:02 ` [poky] " Bruce Ashfield
2012-06-29 13:02 ` Bruce Ashfield
2012-06-29 13:37 ` [poky] " Darren Hart
2012-06-29 13:37 ` Darren Hart
2012-06-29 4:18 ` [PATCH 2/4] linux-yocto: Use INC_PR and move kernel require to linux-yocto.inc Darren Hart
2012-06-29 4:50 ` [poky] " Khem Raj
2012-06-29 4:50 ` Khem Raj
2012-06-29 5:53 ` [poky] " Darren Hart
2012-06-29 5:53 ` Darren Hart
2012-06-29 13:10 ` Bruce Ashfield
2012-06-29 4:18 ` [PATCH 3/4] kernel: Add kernel-headers package for target module build Darren Hart
2012-06-29 4:52 ` Khem Raj
2012-06-29 5:50 ` Darren Hart
2012-06-29 6:04 ` Khem Raj
2012-06-29 6:14 ` Darren Hart [this message]
2012-06-29 7:22 ` Khem Raj
2012-06-29 13:15 ` Bruce Ashfield
2012-06-29 13:36 ` Darren Hart
2012-06-29 13:59 ` Bruce Ashfield
2012-06-29 17:52 ` Khem Raj
2012-06-29 17:58 ` Darren Hart
2012-06-29 4:18 ` [PATCH 4/4] tasl-core-sdk: Add kernel-headers to task-core-sdk RDEPENDS 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=4FED47D7.7080107@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.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 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.