From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <tom.zanussi@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/1][3.2 KERNEL] standard/default/emenlow update
Date: Thu, 26 Apr 2012 16:05:35 -0400 [thread overview]
Message-ID: <4F99AA8F.3010704@windriver.com> (raw)
In-Reply-To: <4F9831B7.4060809@windriver.com>
On 12-04-25 01:17 PM, Bruce Ashfield wrote:
> On 12-04-25 10:11 AM, tom.zanussi@intel.com wrote:
>> From: Tom Zanussi<tom.zanussi@intel.com>
>>
>> This fixes [YOCTO #1669]. Please pull into linux-yocto-3.2.
>>
>> The following changes since commit
>> 86d05af47be45c786c1823a76b6854fa8b411bec:
>> Bruce Ashfield (1):
>> Merge branch 'yocto/standard/base' into standard/default/emenlow
>
> Looks fine. I'll merge this into a spot that only the psb boards
> will pick up, and we won't need any core SRCREV updates .. to stay
> out of the 1.2 release's way.
both emenlow updates are pushed to the 3.2 tree now. Feel free
to update your SRCREVs.
Bruce
>
> Bruce
>
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git
>> tzanussi/drm-lock-fix
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/commit/?h=tzanussi/drm-lock-fix
>>
>>
>> Tom Zanussi (1):
>> bsp/emenlow: give up drm_global_mutex on contention in drm_lock()
>>
>> drivers/gpu/drm-psb/drm_lock.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2012-04-26 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:11 [PATCH 0/1][3.2 KERNEL] standard/default/emenlow update tom.zanussi
2012-04-25 14:11 ` [PATCH 1/1][3.2 KERNEL] bsp/emenlow: give up drm_global_mutex on contention in drm_lock() tom.zanussi
2012-04-25 17:17 ` [PATCH 0/1][3.2 KERNEL] standard/default/emenlow update Bruce Ashfield
2012-04-26 20:05 ` Bruce Ashfield [this message]
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=4F99AA8F.3010704@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@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.