All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [Bug 6945] kernel-dev: multiple kernel build
Date: Tue, 26 May 2015 10:46:04 -0400	[thread overview]
Message-ID: <5564872C.80804@mindchasers.com> (raw)
In-Reply-To: <bug-6945-213-arNSwBAwi6@https.bugzilla.yoctoproject.org/>

Hello,

Does this enhancement only address using the same kernel git branch with 
different .configs to build multiple kernels?

I want to create a single build directory that generates one rootfs but 
has multiple kernels from different git branches and with different 
patch sets applied.

The generated rootfs should have the multiple /lib/module/<uname -r> 
trees created for me.

And I'm wondering how the kernel-devsrc.bb recipe would work in this 
situation?  Would I have multiple preferred kernel providers for my 
multiple kernel builds?

Currently I build multiple kernels outside of yocto and then patch 
things up with my own scripts.

By tracking the bugzilla 6945 enhancement bug, will I know when the 
features have been added to the poky repo so I can try them out?

Thanks

Bob





On 05/12/2015 04:29 PM, bugzilla-daemon@yoctoproject.org wrote:
> Bruce Ashfield <mailto:bruce.ashfield@windriver.com> changed bug 6945
> <https://bugzilla.yoctoproject.org/show_bug.cgi?id=6945>
> What 	Removed 	Added
> Target Milestone 	1.9 	1.9 M3
>
> ------------------------------------------------------------------------
> You are receiving this mail because:
>
>   * You are watching the assignee of the bug.
>   * You are watching someone on the CC list of the bug.
>   * You are watching the reporter of the bug.
>



           reply	other threads:[~2015-05-26 15:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-6945-213-arNSwBAwi6@https.bugzilla.yoctoproject.org/>]

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=5564872C.80804@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=yocto@yoctoproject.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.