From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] linux-yocto: consolidated pull request
Date: Mon, 5 May 2014 10:10:06 -0400 [thread overview]
Message-ID: <cover.1399297986.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's a consolidated pull request for kernel updates and small fixes
that I've queued since the 1.6 release.
The quoting issue was reporting on the mailing list, and I realized
that my fix for it had never been sent, so I dusted it off and here
it is.
As a side effect of that fix, and the fact that there's no way to tell
between a full defconfig and a saved alldefconfig by inspection .. that
offering some guidance in the example custom recipe would be nice.
Everything else is are the -stable and SRCREV updates.
Cheers,
Bruce
The following changes since commit 7b78c364b7de901f97cd8dbe56d5e02f545bf3d3:
cleanup-workdir: Fix crosssdk reference after addition of PN (2014-05-05 09:05:42 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (6):
kernel-yocto: quote kconfig mode check
linux-yocto-custom: provide defconfig guidance
linux-yocto/3.4: update to v3.4.88
linux-yocto/3.10: update to v3.10.38
linux-yocto/3.14: update to v3.14.2
linux-yocto/3.10: mei.cfg: enable Intel chipsets
.../recipes-kernel/linux/linux-yocto-custom.bb | 10 ++++++++++
meta/classes/kernel-yocto.bbclass | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++--------
11 files changed, 58 insertions(+), 48 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-05-05 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 14:10 Bruce Ashfield [this message]
2014-05-05 14:10 ` [PATCH 1/6] kernel-yocto: quote kconfig mode check Bruce Ashfield
2014-05-05 14:10 ` [PATCH 2/6] linux-yocto-custom: provide defconfig guidance Bruce Ashfield
2014-05-05 14:10 ` [PATCH 3/6] linux-yocto/3.4: update to v3.4.88 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 4/6] linux-yocto/3.10: update to v3.10.38 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 5/6] linux-yocto/3.14: update to v3.14.2 Bruce Ashfield
2014-05-05 14:10 ` [PATCH 6/6] linux-yocto/3.10: mei.cfg: enable Intel chipsets Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2014-10-01 4:43 [PATCH 0/6] linux-yocto: consolidated pull request Bruce Ashfield
2015-08-24 13:51 Bruce Ashfield
2015-10-23 20:18 Bruce Ashfield
2016-06-13 15:56 Bruce Ashfield
2016-07-07 18:39 Bruce Ashfield
2018-10-17 13:38 Bruce Ashfield
2020-09-14 22:34 Bruce Ashfield
2021-02-18 3:59 Bruce Ashfield
2021-03-05 3:54 Bruce Ashfield
2024-10-14 13:45 bruce.ashfield
2026-01-14 17:24 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.1399297986.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox