Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yu Ke <ke@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/9] mesa: upgrade to 7.10.2
Date: Sat, 16 Apr 2011 12:38:40 +0800	[thread overview]
Message-ID: <4DA91D50.8060102@linux.intel.com> (raw)
In-Reply-To: <4DA87578.4080809@linux.intel.com>

On 2011/4/16 0:42, Saul Wold wrote:
> On 04/14/2011 10:44 PM, Yu Ke wrote:
>> From: Yu Ke<ke.yu@intel.com>
>>
>> - also remove the talloc-removal.patch because it is already
>>    included in this version
>>
>> Signed-off-by: Yu Ke<ke.yu@intel.com>
>> ---
>>   .../distro/include/preferred-xorg-versions.inc     |    2 +-
>>   .../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 +-
>>   4 files changed, 7 insertions(+), 15580 deletions(-)
>>   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%)
>>
> Ke,
>
> I noticed other patches for both the 7.10.2 version and GIT version in 
> the mesa-dri directory.  Also is there a reason we are carrying around 
> older versions of mesa-dri?
>
> I am looking at the overall clean state of things as we move forward.
>
> Thanks
>     Sau!

Thanks for pointing it out. Yes, I will add Upstream-Status tag to those 
patches. The old versions 7.8.2 is kept for GPLv3 talloc workaround, The 
other old 7.5 and 7.7 version is just legacy recipe from poky. These old 
recipes can be removed safely.  I will make patch to remove it.

BTW, I notice this mesa upgrade patch is already in your staging branch 
(http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=distro/stage), 
so should I make a incremental patch base on this, or make a V3 mesa 
upgrade patch base on master branch?

Regards
Ke



  reply	other threads:[~2011-04-16  4:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  5:44 [PATCH 0/9] recipes upgrade V2 Yu Ke
2011-04-15  5:44 ` [PATCH 1/9] libdrm: upgrade from 2.4.23 to 2.4.25 Yu Ke
2011-04-15  5:44 ` [PATCH 2/9] xf86-input-synaptics: upgrade from 1.3.0 to 1.4.0 Yu Ke
2011-04-15  5:44 ` [PATCH 3/9] xf86-input-vmmouse: upgrade from 12.6.10 to 12.7.0 Yu Ke
2011-04-15  5:44 ` [PATCH 4/9] mesa: upgrade to 7.10.2 Yu Ke
2011-04-15 16:42   ` Saul Wold
2011-04-16  4:38     ` Yu Ke [this message]
2011-04-16  5:06       ` Saul Wold
2011-04-15 19:40   ` Tom Rini
2011-04-16  4:39     ` Yu Ke
2011-04-15  5:44 ` [PATCH 5/9] evieext: upgrade from 1.1.0 to 1.1.1 Yu Ke
2011-04-15  5:44 ` [PATCH 6/9] xf86-input-mouse: upgrade from 1.6 to 1.7 Yu Ke
2011-04-15  5:44 ` [PATCH 7/9] pango: upgrade from 1.28.3 to 1.28.4 Yu Ke
2011-04-15  5:44 ` [PATCH 8/9] xf86-input-keyboard: upgrade from 1.5.0 to 1.6.0 Yu Ke
2011-04-15  5:44 ` [PATCH 9/9] xkbcomp: upgrade from 1.2.0 to 1.2.1 Yu Ke
2011-04-18 21:15 ` [PATCH 0/9] recipes upgrade V2 Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2011-04-11  1:28 [PATCH 0/9] upgrade recipes Yu Ke
2011-04-11  1:28 ` [PATCH 4/9] mesa: upgrade to 7.10.2 Yu Ke

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=4DA91D50.8060102@linux.intel.com \
    --to=ke@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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