From: "André Draszik" <git@andred.net>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases
Date: Wed, 31 Aug 2016 09:54:10 +0100 [thread overview]
Message-ID: <1472633650.12967.15.camel@andred.net> (raw)
In-Reply-To: <78886c10-2951-9a57-31dd-0e1e78d19815@windriver.com>
On Di, 2016-08-30 at 14:35 -0400, Bruce Ashfield wrote:
> Can you clarify for me if you are are using SRC_URI items tagged with
> 'kmeta', i.e. a directory of fragments, or are you just adding .cfg/.scc
> items directly to the SRC_URI ?
I do both:
in the 1st layer, my kernel recipe boils down to:
SRC_URI = "\
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;protocol=git;nocheckout=1;branch=${KBRANCH} \
file://0001-a-patch.patch \
file://kernel-meta;type=kmeta;destsuffix=${KMETA} \
"
KERNEL_FEATURES_append = " patches/some-patches.scc"
KERNEL_FEATURES_append = " patches/more-patches.scc"
KERNEL_FEATURES_append = " patches/even-more-patches.scc"
some of the above in turn include additional .scc items recursively.
In the 2nd layer, my .bbappend boils down to:
FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}-4.4:"
KERNEL_FEATURES_append_tgm = " patches/tgm.scc"
2nd-layer.scc is located in ${THISDIR}/kernel-meta/patches/ in the 2nd
layer. I don't specifically add another SRC_URI item tagged with 'kmeta' (or
any other explicit SRC_URI item for that matter).
Andre'
next prev parent reply other threads:[~2016-08-31 8:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 18:26 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2016-08-15 18:26 ` [PATCH 1/6] linux-yocto/4.1: netfilter: x_tables: fix stable backport Bruce Ashfield
2016-08-15 18:26 ` [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29 Bruce Ashfield
2016-08-18 15:15 ` Richard Purdie
2016-08-18 15:16 ` Bruce Ashfield
2016-08-18 15:20 ` Richard Purdie
2016-08-19 14:57 ` Bruce Ashfield
2016-08-24 11:25 ` Richard Purdie
2016-08-24 13:14 ` Bruce Ashfield
2016-08-15 18:26 ` [PATCH 3/6] linux-yocto/4.1: config updates Bruce Ashfield
2016-08-15 18:26 ` [PATCH 4/6] linux-yocto/4.4: -rt update patch meta-data to remove () Bruce Ashfield
2016-08-15 18:26 ` [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases Bruce Ashfield
2016-08-30 9:05 ` André Draszik
2016-08-30 13:05 ` Bruce Ashfield
2016-08-30 14:19 ` André Draszik
2016-08-30 18:35 ` Bruce Ashfield
2016-08-31 8:54 ` André Draszik [this message]
2016-08-31 20:17 ` Bruce Ashfield
2016-09-01 16:14 ` André Draszik
2016-09-01 20:21 ` Bruce Ashfield
2016-09-02 3:18 ` Bruce Ashfield
2016-09-02 4:37 ` Bruce Ashfield
2016-08-15 18:27 ` [PATCH 6/6] yocto-bsp/yocto-kernel: update to work with the latest kern-tools Bruce Ashfield
2016-08-16 16:00 ` [PATCH 0/6] kernel-yocto: consolidated pull request Burton, Ross
2016-08-16 16:01 ` Bruce Ashfield
2016-08-16 16:10 ` Burton, Ross
2016-08-16 16:11 ` Bruce Ashfield
2016-08-16 16:15 ` Burton, Ross
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=1472633650.12967.15.camel@andred.net \
--to=git@andred.net \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox