From: Saul Wold <saul.wold@intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/5] upgrade xserver v2
Date: Mon, 22 Nov 2010 09:49:15 -0800 [thread overview]
Message-ID: <4CEAAD1B.7010200@intel.com> (raw)
In-Reply-To: <cover.1290097804.git.ke.yu@intel.com>
On 11/18/2010 08:30 AM, Yu Ke wrote:
> accodring to Saul's comments, V2 patch has the following changes
> - add clear explanation on the commit message.
> - correct the license check sum and test it
> against latest poky/master
> - add SRI_URI checksum
> - mesa/cairo related recpies(mesa, talloc, libxml2,cairo) are still hold,
> as one time build failure are observed. Although the failure
> disappers after build again, it is better to find out the reason
> before submitting it.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: kyu3/upgrade-11-18
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/upgrade-11-18
>
> Thanks,
> Yu Ke<ke.yu@intel.com>
> ---
>
>
> Yu Ke (5):
> libdrm: upgrade from 2.4.21 to 2.4.22
> xf86-video-intel: upgrade from 2.12.0 to 2.13.0
> xserver-xf86-dri-lite: upgrade from 1.9.0 rc4 to 1.9.2
> xrandr: upgrade from 1.3.2 to 1.3.4
> pixman: upgrade from 0.18.2 to 0.20.0
>
> .../distro/include/preferred-xorg-versions.inc | 10 +++---
> .../installtests.patch | 0
> meta/recipes-graphics/drm/libdrm_2.4.21.bb | 4 --
> meta/recipes-graphics/drm/libdrm_2.4.22.bb | 7 ++++
> .../xorg-app/xrandr/resolve_symbol_clash.patch | 33 --------------------
> .../xorg-app/{xrandr_1.3.2.bb => xrandr_1.3.4.bb} | 3 +-
> ...-intel_2.12.0.bb => xf86-video-intel_2.13.0.bb} | 3 ++
> .../{pixman_0.18.2.bb => pixman_0.20.0.bb} | 3 ++
> ....8.99.904.bb => xserver-xf86-dri-lite_1.9.2.bb} | 5 ++-
> 9 files changed, 24 insertions(+), 44 deletions(-)
> rename meta/recipes-graphics/drm/{libdrm-2.4.21 => libdrm-2.4.22}/installtests.patch (100%)
> delete mode 100644 meta/recipes-graphics/drm/libdrm_2.4.21.bb
> create mode 100644 meta/recipes-graphics/drm/libdrm_2.4.22.bb
> delete mode 100644 meta/recipes-graphics/xorg-app/xrandr/resolve_symbol_clash.patch
> rename meta/recipes-graphics/xorg-app/{xrandr_1.3.2.bb => xrandr_1.3.4.bb} (61%)
> rename meta/recipes-graphics/xorg-driver/{xf86-video-intel_2.12.0.bb => xf86-video-intel_2.13.0.bb} (67%)
> rename meta/recipes-graphics/xorg-lib/{pixman_0.18.2.bb => pixman_0.20.0.bb} (80%)
> rename meta/recipes-graphics/xorg-xserver/{xserver-xf86-dri-lite_1.8.99.904.bb => xserver-xf86-dri-lite_1.9.2.bb} (76%)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Pulled into Master
Thanks
Sau!
prev parent reply other threads:[~2010-11-22 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 16:30 [PATCH 0/5] upgrade xserver v2 Yu Ke
2010-11-15 13:01 ` [PATCH 5/5] pixman: upgrade from 0.18.2 to 0.20.0 Yu Ke
2010-11-16 6:39 ` [PATCH 1/5] libdrm: upgrade from 2.4.21 to 2.4.22 Yu Ke
2010-11-16 13:25 ` [PATCH 3/5] xserver-xf86-dri-lite: upgrade from 1.9.0 rc4 to 1.9.2 Yu Ke
2010-11-16 13:50 ` [PATCH 2/5] xf86-video-intel: upgrade from 2.12.0 to 2.13.0 Yu Ke
2010-11-16 13:58 ` [PATCH 4/5] xrandr: upgrade from 1.3.2 to 1.3.4 Yu Ke
2010-11-22 17:49 ` Saul Wold [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=4CEAAD1B.7010200@intel.com \
--to=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox