All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Ke <ke.yu@intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/9] upgrade recipes
Date: Tue, 12 Apr 2011 15:32:55 +0800	[thread overview]
Message-ID: <4DA40027.9040808@intel.com> (raw)
In-Reply-To: <4DA344C7.1050104@intel.com>

on 2011-4-12 2:13, Saul Wold wrote:
> On 04/10/2011 06:28 PM, Yu Ke wrote:
>> From: Yu Ke<ke.yu@intel.com>
>>
>> upgrade the following recipes to latest version:
>>
>> libdrm
>> xf86-input-synaptics
>> xf86-input-vmmouse
>> mesa
>> evieext
>> xf86-input-mouse
>> pango
>> xf86-input-keyboard
>> xkbcomp
>>
> I noticed a number of these recipes have patches, but I did not see any
> addition of the Upstream-Status: tag to those patches. Please, as we are
> doing recipe updating, add the Upstream-Status tag, if at a minimul with
> a status of pending.
>
> Sau!

I see. I will send a separate patch set to add those upstream status.

Regards
Ke

>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>> Branch: kyu3/upgrade-04-11
>> Browse:
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/upgrade-04-11
>>
>> Thanks,
>> Yu Ke<ke.yu@intel.com>
>> ---
>>
>>
>> Yu Ke (9):
>> libdrm: upgrade from 2.4.23 to 2.4.24
>> xf86-input-synaptics: upgrade from 1.3.0 to 1.4.0
>> xf86-input-vmmouse: upgrade from 12.6.10 to 12.7.0
>> mesa: upgrade to 7.10.2
>> evieext: upgrade from 1.1.0 to 1.1.1
>> xf86-input-mouse: upgrade from 1.6 to 1.7
>> pango: upgrade from 1.28.3 to 1.28.4
>> xf86-input-keyboard: upgrade from 1.5.0 to 1.6.0
>> xkbcomp: upgrade from 1.2.0 to 1.2.1
>>
>> .../distro/include/preferred-xorg-versions.inc | 12 +-
>> .../installtests.patch | 0
>> .../drm/{libdrm_2.4.23.bb => libdrm_2.4.24.bb} | 4 +-
>> .../mesa/files/talloc-removal.patch |15571 --------------------
>> .../mesa/{mesa-dri_7.10.bb => mesa-dri_7.10.2.bb} | 7 +-
>> .../{mesa-xlib_7.10.bb => mesa-xlib_7.10.2.bb} | 7 +-
>> .../{pango-1.28.3 => pango-1.28.4}/no-tests.patch | 0
>> .../pango/{pango_1.28.3.bb => pango_1.28.4.bb} | 4 +-
>> .../xorg-app/xkbcomp/cross-compile-fix.patch | 35 -
>> .../{xkbcomp_1.2.0.bb => xkbcomp_1.2.1.bb} | 5 +-
>> ...board_1.5.0.bb => xf86-input-keyboard_1.6.0.bb} | 4 +-
>> ...ut-mouse_1.6.0.bb => xf86-input-mouse_1.7.0.bb} | 4 +-
>> ...tics_1.3.0.bb => xf86-input-synaptics_1.4.0.bb} | 4 +-
>> ...use_12.6.10.bb => xf86-input-vmmouse_12.7.0.bb} | 4 +-
>> .../{evieext_1.1.0.bb => evieext_1.1.1.bb} | 8 +-
>> 15 files changed, 30 insertions(+), 15639 deletions(-)
>> rename meta/recipes-graphics/drm/{libdrm-2.4.23 =>
>> libdrm-2.4.24}/installtests.patch (100%)
>> rename meta/recipes-graphics/drm/{libdrm_2.4.23.bb =>
>> libdrm_2.4.24.bb} (54%)
>> delete mode 100644 meta/recipes-graphics/mesa/files/talloc-removal.patch
>> rename meta/recipes-graphics/mesa/{mesa-dri_7.10.bb =>
>> mesa-dri_7.10.2.bb} (85%)
>> rename meta/recipes-graphics/mesa/{mesa-xlib_7.10.bb =>
>> mesa-xlib_7.10.2.bb} (68%)
>> rename meta/recipes-graphics/pango/{pango-1.28.3 =>
>> pango-1.28.4}/no-tests.patch (100%)
>> rename meta/recipes-graphics/pango/{pango_1.28.3.bb =>
>> pango_1.28.4.bb} (50%)
>> delete mode 100644
>> meta/recipes-graphics/xorg-app/xkbcomp/cross-compile-fix.patch
>> rename meta/recipes-graphics/xorg-app/{xkbcomp_1.2.0.bb =>
>> xkbcomp_1.2.1.bb} (72%)
>> rename meta/recipes-graphics/xorg-driver/{xf86-input-keyboard_1.5.0.bb
>> => xf86-input-keyboard_1.6.0.bb} (74%)
>> rename meta/recipes-graphics/xorg-driver/{xf86-input-mouse_1.6.0.bb =>
>> xf86-input-mouse_1.7.0.bb} (76%)
>> rename
>> meta/recipes-graphics/xorg-driver/{xf86-input-synaptics_1.3.0.bb =>
>> xf86-input-synaptics_1.4.0.bb} (83%)
>> rename
>> meta/recipes-graphics/xorg-driver/{xf86-input-vmmouse_12.6.10.bb =>
>> xf86-input-vmmouse_12.7.0.bb} (64%)
>> rename meta/recipes-graphics/xorg-proto/{evieext_1.1.0.bb =>
>> evieext_1.1.1.bb} (54%)
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>



  reply	other threads:[~2011-04-12  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  1:28 [PATCH 0/9] upgrade recipes Yu Ke
2011-04-11  1:28 ` [PATCH 1/9] libdrm: upgrade from 2.4.23 to 2.4.24 Yu Ke
2011-04-11  1:28 ` [PATCH 2/9] xf86-input-synaptics: upgrade from 1.3.0 to 1.4.0 Yu Ke
2011-04-11  1:28 ` [PATCH 3/9] xf86-input-vmmouse: upgrade from 12.6.10 to 12.7.0 Yu Ke
2011-04-11  1:28 ` [PATCH 4/9] mesa: upgrade to 7.10.2 Yu Ke
2011-04-11  1:28 ` [PATCH 5/9] evieext: upgrade from 1.1.0 to 1.1.1 Yu Ke
2011-04-11 18:13   ` [poky] " Saul Wold
2011-04-11 18:13     ` Saul Wold
2011-04-12  7:23     ` [poky] " Yu Ke
2011-04-12  7:23       ` [OE-core] " Yu Ke
2011-04-11  1:28 ` [PATCH 6/9] xf86-input-mouse: upgrade from 1.6 to 1.7 Yu Ke
2011-04-11  1:28 ` [PATCH 7/9] pango: upgrade from 1.28.3 to 1.28.4 Yu Ke
2011-04-11  1:28 ` [PATCH 8/9] xf86-input-keyboard: upgrade from 1.5.0 to 1.6.0 Yu Ke
2011-04-11  1:28 ` [PATCH 9/9] xkbcomp: upgrade from 1.2.0 to 1.2.1 Yu Ke
2011-04-11 18:13 ` [PATCH 0/9] upgrade recipes Saul Wold
2011-04-12  7:32   ` Yu Ke [this message]
2011-04-18 21:28 ` [poky] " Saul Wold
2011-04-18 21:28   ` Saul Wold

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=4DA40027.9040808@intel.com \
    --to=ke.yu@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@intel.com \
    /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.