From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] kernel-yocto: (small) consolidated pull request
Date: Tue, 18 Oct 2016 21:08:16 -0400 [thread overview]
Message-ID: <cover.1476839114.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Here are two patches that I've been carrying that are safe for the
2.2 release. I have other patches/fixes and -stable updates in my
queue, but I'm going to hold them back until after the release in
the name of stability.
We have one configuration cleanup patch, and a kern tools change
to allow patches with things like () ;, etc in their names (I
ran into this when refreshing the preempt-rt series today and it
has patches with () in their name.
Cheers,
Bruce
The following changes since commit 4b94b498e21aeba945fe7e72a6b7c4bb0314fb83:
bitbake: toaster: Update default release to Morty (2016-10-15 13:21:54 +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 (2):
linux-yocto/4.4/4.8: kernel config warning cleanups
kern-tools: make patches with shell-unsafe characters valid
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.8.bb | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
--
2.5.0
next reply other threads:[~2016-10-19 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 1:08 Bruce Ashfield [this message]
2016-10-19 1:08 ` [PATCH 1/2] linux-yocto/4.4/4.8: kernel config warning cleanups Bruce Ashfield
2016-10-19 1:08 ` [PATCH 2/2] kern-tools: make patches with shell-unsafe characters valid 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.1476839114.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