From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Eric Bénard" <eric@eukrea.com>
Cc: mark.asselstine@windriver.com, poky@yoctoproject.org
Subject: Re: [PATCH 1/1] linux-yocto-bsps: update hardware reference BSPs to v3.4.11
Date: Mon, 08 Oct 2012 10:23:52 +0100 [thread overview]
Message-ID: <1349688232.15658.104.camel@ted> (raw)
In-Reply-To: <20121008102455.02a03cd3@eb-e6520>
On Mon, 2012-10-08 at 10:24 +0200, Eric Bénard wrote:
> Hi Bruce,
>
> Le Sun, 7 Oct 2012 23:41:31 -0400,
> Bruce Ashfield <bruce.ashfield@windriver.com> a écrit :
>
> > The hardware reference BSPs are missing the update to 3.4.11
> > that the qemu* machines received several weeks ago.
> >
> > Bumping to 3.4.11 specifically addresses the segfaults being
> > seen with rpm on the beagleboard.
> >
> 3.4.13 is out maybe worth to directly update to the latest stable ?
At this point, 3.4.11 has had some testing, we've not done any testing
with 3.4.13.
The trouble is we're due -rc4 tomorrow which is our final build for the
release. I'm extremely reluctant to make *any* kernel changes at this
point but it looks like this segfault issue is going to force my hand
and I'm going to have to take the update.
I'm already doing some mitigation type work of pretesting the builds in
advance to try and ensure -rc4 is successful and we can take this
change. Adding 3.4.13 into the mix sounds nice in theory but
substantially increases the risk. Keep in mind this bug we're trying to
fix crept in through the "stable" updates in the first place :(
Cheers,
Richard
next prev parent reply other threads:[~2012-10-08 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 3:41 [PATCH 0/1] linux-yocto-bsps: bump reference BSPs to v3.4.11 Bruce Ashfield
2012-10-08 3:41 ` [PATCH 1/1] linux-yocto-bsps: update hardware " Bruce Ashfield
2012-10-08 8:24 ` Eric Bénard
2012-10-08 9:23 ` Richard Purdie [this message]
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=1349688232.15658.104.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=eric@eukrea.com \
--cc=mark.asselstine@windriver.com \
--cc=poky@yoctoproject.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.