From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] linux-yocto/3.10: update to v3.10.11
Date: Tue, 10 Sep 2013 11:50:57 -0400 [thread overview]
Message-ID: <cover.1378827962.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
I realize we are working our way through the stabilization cycle, and
this -stable update is of particular interest, the patch says it
all:
Bumping to the 3.10.11 -stable release. Of note in this update is
the timer_list fix, which broke ssh access in the previous 3.10
series of updates:
timer_list: correct the iterator for timer_list
commit 84a78a6504f5c5394a8e558702e5b54131f01d14 upstream.
With this, we can revert the two temporary fixes for timer lists.
ssh access has been directly tested after this update.
And here's my test results:
[/home/bruc...poky/build]> ssh root@192.168.7.2
root@qemux86-64:~# uname -a
Linux qemux86-64 3.10.11-yocto-standard #1 SMP PREEMPT Tue Sep 10 03:29:54 EDT 2013 x86_64 GNU/Linux
root@qemux86-64:~#
Cheers,
Bruce
The following changes since commit 2ab1bf27f79beadc45e86a26c85fc0b95ae3496f:
bitbake: prserv: Ensure data is committed (2013-09-08 10:51:56 +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 (1):
linux-yocto/3.10: bump kver to 3.10.11
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++++++---------
3 files changed, 16 insertions(+), 16 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-09-10 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 15:50 Bruce Ashfield [this message]
2013-09-10 15:50 ` [PATCH 1/1] linux-yocto/3.10: bump kver to 3.10.11 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.1378827962.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