From: <zhe.he@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v3 0/2] Yocto Bug #6945
Date: Wed, 24 Feb 2016 07:20:08 -0500 [thread overview]
Message-ID: <cover.1456315808.git.zhe.he@windriver.com> (raw)
From: He Zhe <zhe.he@windriver.com>
v1 to v2:
- Change KERNEL_OUTPUT to KERNEL_OUTPUT_DIR and update comments
- Update related doc files
- Replace all KERNEL_ALT_IMAGETYPEs with KERNEL_IMAGETYPES
- Link built vmlinuz to boot directory for reference
v2 to v3:
- Merge existing KERNEL_ALT_IMAGETYPE into KERNEL_IMAGETYPES in order that users can still use the old variables.
- Run oe_rummake in a loop for every types so that we can add different configurations to them easily in the future.
- Warn, intead of die, users if one of the types are over the size limit.
- Remove the replacement of KERNEL_ALT_IMAGETYPE in v2.
- Remove the doc parts. They will be submitted yocto-docs later.
- Change some grep usage to make it more clear.
- Correct a typo.
The following changes since commit 23056103c949b498c23b47579e8dd57ce78e6ed9:
uclibc: Do not use immediate expansion operator (2016-02-22 20:42:48 +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 dc52a1efbb8248ea274a1cd0cca5734290b3025f:
kernel: Make symbol link to vmlinuz in boot directory (2016-02-24 07:08:16 -0500)
----------------------------------------------------------------
He Zhe (2):
kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time
kernel: Make symbol link to vmlinuz in boot directory
meta/classes/kernel-fitimage.bbclass | 20 ++++++++-------
meta/classes/kernel-grub.bbclass | 44 +++++++++++++++++++++-----------
meta/classes/kernel-uimage.bbclass | 22 ++++++++--------
meta/classes/kernel.bbclass | 187 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------
meta/conf/documentation.conf | 3 ++-
meta/recipes-kernel/linux/linux-dtb.inc | 49 ++++++++++++++++++++++--------------
meta/recipes-kernel/linux/linux-yocto.inc | 2 +-
7 files changed, 218 insertions(+), 109 deletions(-)
He Zhe (2):
kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time
kernel: Make symbol link to vmlinuz in boot directory
meta/classes/kernel-fitimage.bbclass | 20 ++--
meta/classes/kernel-grub.bbclass | 44 ++++---
meta/classes/kernel-uimage.bbclass | 22 ++--
meta/classes/kernel.bbclass | 187 +++++++++++++++++++++---------
meta/conf/documentation.conf | 3 +-
meta/recipes-kernel/linux/linux-dtb.inc | 49 +++++---
meta/recipes-kernel/linux/linux-yocto.inc | 2 +-
7 files changed, 218 insertions(+), 109 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-24 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 12:20 zhe.he [this message]
2016-02-24 12:20 ` [PATCH v3 1/2] kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time zhe.he
2016-02-24 12:20 ` [PATCH v3 2/2] kernel: Make symbol link to vmlinuz in boot directory zhe.he
2016-03-11 3:32 ` [PATCH v3 0/2] Yocto Bug #6945 He Zhe
2016-03-22 2:31 ` He Zhe
2016-03-22 3:37 ` Bruce Ashfield
2016-03-22 18:29 ` Bruce Ashfield
2016-04-05 8:49 ` He Zhe
2016-04-05 14:43 ` Bruce Ashfield
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.1456315808.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox