From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: mark.asselstine@windriver.com, poky@yoctoproject.org
Subject: [PATCH 0/1] linux-yocto-bsps: bump reference BSPs to v3.4.11
Date: Sun, 7 Oct 2012 23:41:30 -0400 [thread overview]
Message-ID: <cover.1349666145.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
I'm out of the office until Wednesday, but wanted to send this
change before then. I'm attempting to relay this via gmail smtp,
so I hope the patches come through properly.
We were looking at YOCTO 3186 (which is a segfault when running
rpm commands), and Mark Asselstine bisected it to a regression
introduced in v3.4.10 which was subsequently fixed in 3.4.11.
Luckily I had already bumped the qemu BSPs to 3.4.11, so updating
the hardware reference boards to the already in tree version fixes
the regression.
(random note: -stable is up to 3.4.13, but there are no firm plans
to send those changes at this point).
Send any questions about this to my gmail account, since I won't
have access to my work email until Wednesday.
Cheers,
Bruce
cc: Mark Asselstine <mark.asselstine@windriver.com>
The following changes since commit eb8ac50d58575be3e04c4decc5b0e2d80381be9b:
documentation: dev-manual - mentioned SRC_URI in the kernel example (2012-10-07 13:15:37 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/yocto-bsps
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/yocto-bsps
Bruce Ashfield (1):
linux-yocto-bsps: update hardware reference BSPs to v3.4.11
.../recipes-kernel/linux/linux-yocto_3.4.bbappend | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-10-08 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 3:41 Bruce Ashfield [this message]
2012-10-08 3:41 ` [PATCH 1/1] linux-yocto-bsps: update hardware reference BSPs to v3.4.11 Bruce Ashfield
2012-10-08 8:24 ` Eric Bénard
2012-10-08 9:23 ` Richard Purdie
2012-10-08 9:29 ` Eric Bénard
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.1349666145.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=mark.asselstine@windriver.com \
--cc=poky@yoctoproject.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 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.