skeleton: clarify linux-yocto-custom workflow
It was pointed out that the kernel development documentation recommends making a copy of linux-yocto-custom, while the comments in the recipe itself suggest a bbappend. To keep things consistent between these two sources, we update the comment in the recipe itself to also recommend a copy (and rename). [YOCTO: #6925] (From OE-Core rev: aabd47e46a31b526ee880dfd22a1a1f2831ab355) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
dbfafd8493
commit
6e1ba48120
|
@ -4,11 +4,9 @@
|
|||
# kernel classes to apply a subset of yocto kernel management to git
|
||||
# managed kernel repositories.
|
||||
#
|
||||
# To use linux-yocto-custom in your layer, create a
|
||||
# linux-yocto-custom.bbappend file containing at least the following
|
||||
# lines:
|
||||
# To use linux-yocto-custom in your layer, copy this recipe (optionally
|
||||
# rename it as well) and modify it appropriately for your machine. i.e.:
|
||||
#
|
||||
# FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
|
||||
# COMPATIBLE_MACHINE_yourmachine = "yourmachine"
|
||||
#
|
||||
# You must also provide a Linux kernel configuration. The most direct
|
||||
|
|
Loading…
Reference in New Issue