All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/5] skeleton: clarify linux-yocto-custom workflow
Date: Tue, 24 Mar 2015 14:57:53 -0400	[thread overview]
Message-ID: <1c63179dfe46a004623f41434957fc34fe23d7e6.1427222980.git.bruce.ashfield@windriver.com> (raw)
In-Reply-To: <cover.1427222980.git.bruce.ashfield@windriver.com>

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]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
index b1a0784c1b7d..05463c026304 100644
--- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
+++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
@@ -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
-- 
2.1.0



  parent reply	other threads:[~2015-03-24 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 18:57 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2015-03-24 18:57 ` [PATCH 1/5] kernel-yocto: allow in-tree defconfigs Bruce Ashfield
2015-03-24 18:57 ` [PATCH 2/5] linux-yocto/3.19: configuration updates and stable import Bruce Ashfield
2015-03-24 18:57 ` [PATCH 3/5] linux-yocto/3.14: integrate korg stable and meta data changes Bruce Ashfield
2015-03-24 18:57 ` [PATCH 4/5] linux-yocto/3.19: fixes for Intel core warnings Bruce Ashfield
2015-04-13 23:11   ` Martin Jansa
2015-03-24 18:57 ` Bruce Ashfield [this message]
2015-03-25  9:26 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2015-03-25 12:13   ` Bruce Ashfield
2015-03-25 13:26     ` Bruce Ashfield
2015-03-25 13:52       ` Richard Purdie

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=1c63179dfe46a004623f41434957fc34fe23d7e6.1427222980.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.