public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] module.bbclass: Allow for modules to be packaged seperate from ${PN}
Date: Wed, 30 Jan 2013 16:30:50 -0800	[thread overview]
Message-ID: <5109BB3A.1060008@linux.intel.com> (raw)
In-Reply-To: <5109B893.2070906@linux.intel.com>



On 01/30/2013 04:19 PM, Saul Wold wrote:
> On 01/30/2013 04:03 PM, Darren Hart wrote:
>> On 01/30/2013 03:05 PM, Saul Wold wrote:
>>> This patch will allow recipes that provide kernel modules to package
>>> the module or modules in specific packages. That list is contained in
>>> MODULE_PACKAGES, this defaults to  to preserve the current behavior.
>>
>> s/to to preserve/to preserving/
>>
> Fixed in my MUT branch
> 
>>> The package can also define MODULE_FILES to specify files.
>>
>> So, for example, the hello-mod recipe in meta-skeleton can remain unchanged?
> Correct, the default for MODULE_PACKAGES is "${PN}" so no changes are 
> required.
> 
>> It will then get /lib/modules/*/hello.ko in FILES_hello-mod and
>> MODULE_PACKAGES will be set to hello-mod. If I wanted to, hello-mod
>> could create to modules, and package them separately by specifying two
>> values in MODULE_PACKAGES and creating the appropriate
>> MODULE_FILES_foo|bar entries?
>>
> Correct, 2 packages would be created and the files specified would be 
> packaged into foo and bar.
> 
>> Right, seems to make sense to me. What testing has this seen? Have you
>> verified it with hello-mod?
>>
> I verified it with lttng-module and added MODULE_PACKAGES = 
> "module-test" and MODULE_FILES_module-test = "/etc" and then verified 
> packages and variables.
> 
> Sau!
> 
>> --
>> Darren
>>
>>>
>>> [YOCTO #3803]
>>>
>>> Signed-off-by: Saul Wold <sgw@linux.intel.com>

Acked-by: Darren Hart <dvhart@linux.intel.com>

Thanks Saul!

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel



      reply	other threads:[~2013-01-31  0:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 23:05 [PATCH] module.bbclass: Allow for modules to be packaged seperate from ${PN} Saul Wold
2013-01-31  0:03 ` Darren Hart
2013-01-31  0:19   ` Saul Wold
2013-01-31  0:30     ` Darren Hart [this message]

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=5109BB3A.1060008@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.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