From: <zhe.he@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Yocto Bug #6945
Date: Wed, 17 Feb 2016 05:01:27 -0500 [thread overview]
Message-ID: <cover.1455702479.git.zhe.he@windriver.com> (raw)
From: He Zhe <zhe.he@windriver.com>
This patch has been discussed previously and modified according to Richard's
suggestions, and adjusted against the latest code context.
The following changes since commit 152914f2983c5d69001de1d46ce99547fa1e75fe:
oeqa/parselogs: Whitelist dmi firmware failure message in 4.4 kernels (2016-02-16 23:54:05 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib zhe/yocto-bug-6945
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=zhe/yocto-bug-6945
for you to fetch changes up to d36ac8034f8914c57c27a514b9a692c3c1377f42:
kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time (2016-02-17 04:37:59 -0500)
----------------------------------------------------------------
He Zhe (1):
kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time
meta/classes/kernel-fitimage.bbclass | 20 ++--
meta/classes/kernel-grub.bbclass | 44 ++++++---
meta/classes/kernel-uimage.bbclass | 22 +++--
meta/classes/kernel.bbclass | 169 ++++++++++++++++++++++----------
meta/conf/documentation.conf | 1 +
meta/recipes-kernel/linux/linux-dtb.inc | 49 +++++----
6 files changed, 202 insertions(+), 103 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-17 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:01 zhe.he [this message]
2016-02-17 10:01 ` [PATCH 1/1] kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time zhe.he
2016-02-18 3:37 ` Andre McCurdy
2016-02-18 8:15 ` Andrea Adami
2016-02-18 10:16 ` He Zhe
2016-02-18 9:49 ` He Zhe
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=cover.1455702479.git.zhe.he@windriver.com \
--to=zhe.he@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 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.